terribleplan/next.js
1
0
Fork 0
mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00
Code Issues Releases Wiki Activity
next.js/examples/with-jest-typescript/package.json

31 lines
722 B
JSON
Raw Normal View History

Added with-jest-typescript example (#4124) * Added with-jest-typescript example with files and readme * Updated package.json As per the comment, updated the package.json so the info is same as in other examples. * Proper name in package.json
2018-04-13 14:53:59 +00:00
{
"name": "with-jest-typescript",
"version": "1.0.0",
"scripts": {
Upgrade with-jest-typescript example to next 6.0.0 (#4543) Hello! I ran into an issue using typescript and jest with next 6.0.0. I was able to work through fixing it and I wanted to share my solution back to next.js, by upgrading the with-jest-typescript example to next 6.0.0. The steps I followed were: 1. `npx babel-upgrade --write` which added babel-core@^7.0.0-bridge.0 to allow jest's babel 6 to play nice with next's babel 7 2. Remove `ts-jest` and replace with `babel-jest` to use babel to transform the typescript code, as is done when the dev and production builds run 3. Update the babelrc to use commonjs modules in test mode to be compatible with jest Also, I removed the `NODE_ENV=test` on the jest task, because jest sets the env to test anyways, and I'm on windows where this code is incorrect. The other option is to use `cross-env` but I felt it was simpler to just remove the environment override. To my knowledge, this PR would help on the following issues: #3663 #4227 #4531 #4528 #4239
2018-06-06 08:31:21 +00:00
"test": "jest",
Added with-jest-typescript example (#4124) * Added with-jest-typescript example with files and readme * Updated package.json As per the comment, updated the package.json so the info is same as in other examples. * Proper name in package.json
2018-04-13 14:53:59 +00:00
"dev": "next",
"build": "next build",
"start": "next start"
},
"dependencies": {
Upgrade with-jest-typescript example to next 6.0.0 (#4543) Hello! I ran into an issue using typescript and jest with next 6.0.0. I was able to work through fixing it and I wanted to share my solution back to next.js, by upgrading the with-jest-typescript example to next 6.0.0. The steps I followed were: 1. `npx babel-upgrade --write` which added babel-core@^7.0.0-bridge.0 to allow jest's babel 6 to play nice with next's babel 7 2. Remove `ts-jest` and replace with `babel-jest` to use babel to transform the typescript code, as is done when the dev and production builds run 3. Update the babelrc to use commonjs modules in test mode to be compatible with jest Also, I removed the `NODE_ENV=test` on the jest task, because jest sets the env to test anyways, and I'm on windows where this code is incorrect. The other option is to use `cross-env` but I felt it was simpler to just remove the environment override. To my knowledge, this PR would help on the following issues: #3663 #4227 #4531 #4528 #4239
2018-06-06 08:31:21 +00:00
"next": "^6.0.0",
Test updater script on examples folder (#5993) I wrote a [script](https://github.com/j0lv3r4/dependency-version-updater) to update dependencies recursively in `package.json` files, e.g.: ``` $ node index.js --path="./examples" --dependencies="react=^16.7.0,react-dom=^16.7.0" ``` This PR contains the result against the examples folder.
2019-01-05 11:19:27 +00:00
"react": "^16.7.0",
"react-dom": "^16.7.0"
Added with-jest-typescript example (#4124) * Added with-jest-typescript example with files and readme * Updated package.json As per the comment, updated the package.json so the info is same as in other examples. * Proper name in package.json
2018-04-13 14:53:59 +00:00
},
"devDependencies": {
Upgrade with-jest-typescript example to next 6.0.0 (#4543) Hello! I ran into an issue using typescript and jest with next 6.0.0. I was able to work through fixing it and I wanted to share my solution back to next.js, by upgrading the with-jest-typescript example to next 6.0.0. The steps I followed were: 1. `npx babel-upgrade --write` which added babel-core@^7.0.0-bridge.0 to allow jest's babel 6 to play nice with next's babel 7 2. Remove `ts-jest` and replace with `babel-jest` to use babel to transform the typescript code, as is done when the dev and production builds run 3. Update the babelrc to use commonjs modules in test mode to be compatible with jest Also, I removed the `NODE_ENV=test` on the jest task, because jest sets the env to test anyways, and I'm on windows where this code is incorrect. The other option is to use `cross-env` but I felt it was simpler to just remove the environment override. To my knowledge, this PR would help on the following issues: #3663 #4227 #4531 #4528 #4239
2018-06-06 08:31:21 +00:00
"@types/jest": "^23.0.0",
Added with-jest-typescript example (#4124) * Added with-jest-typescript example with files and readme * Updated package.json As per the comment, updated the package.json so the info is same as in other examples. * Proper name in package.json
2018-04-13 14:53:59 +00:00
"@types/next": "^2.4.8",
"@types/react": "^16.0.41",
"@types/react-dom": "^16.0.4",
Fix typescript examples (#4704) Update @zeit/next-typescript version on examples using it
2018-06-30 20:23:38 +00:00
"@zeit/next-typescript": "1.1.0",
Upgrade with-jest-typescript example to next 6.0.0 (#4543) Hello! I ran into an issue using typescript and jest with next 6.0.0. I was able to work through fixing it and I wanted to share my solution back to next.js, by upgrading the with-jest-typescript example to next 6.0.0. The steps I followed were: 1. `npx babel-upgrade --write` which added babel-core@^7.0.0-bridge.0 to allow jest's babel 6 to play nice with next's babel 7 2. Remove `ts-jest` and replace with `babel-jest` to use babel to transform the typescript code, as is done when the dev and production builds run 3. Update the babelrc to use commonjs modules in test mode to be compatible with jest Also, I removed the `NODE_ENV=test` on the jest task, because jest sets the env to test anyways, and I'm on windows where this code is incorrect. The other option is to use `cross-env` but I felt it was simpler to just remove the environment override. To my knowledge, this PR would help on the following issues: #3663 #4227 #4531 #4528 #4239
2018-06-06 08:31:21 +00:00
"babel-core": "^7.0.0-bridge.0",
Fix with-jest-typescript example to keep babel-jest in sync with jest (#5941) This fixes the `with-jest-typescript` example to keep jest in sync with babel-jest (also updated to the latest of both). Having them resolve to different versions was resulting in weird errors. When attempting to update the `transform` property in `jest.setup.js` to add babel-jest support to *.js/jsx files, it would throw: > Plugin 0 specified in "node_modules/next/babel.js" provided an invalid property of "default" (While processing preset: "node_modules/next/babel.js") Indirectly, this will fix https://github.com/zeit/next.js/issues/5917, once the author updates `jest.setup.js` to have: ```js transform: { '^.+\\.(js|tsx)?$': 'babel-jest', }, ```
2018-12-23 20:55:35 +00:00
"babel-jest": "^23.6.0",
Added with-jest-typescript example (#4124) * Added with-jest-typescript example with files and readme * Updated package.json As per the comment, updated the package.json so the info is same as in other examples. * Proper name in package.json
2018-04-13 14:53:59 +00:00
"enzyme": "^3.3.0",
"enzyme-adapter-react-16": "^1.1.1",
Fix with-jest-typescript example to keep babel-jest in sync with jest (#5941) This fixes the `with-jest-typescript` example to keep jest in sync with babel-jest (also updated to the latest of both). Having them resolve to different versions was resulting in weird errors. When attempting to update the `transform` property in `jest.setup.js` to add babel-jest support to *.js/jsx files, it would throw: > Plugin 0 specified in "node_modules/next/babel.js" provided an invalid property of "default" (While processing preset: "node_modules/next/babel.js") Indirectly, this will fix https://github.com/zeit/next.js/issues/5917, once the author updates `jest.setup.js` to have: ```js transform: { '^.+\\.(js|tsx)?$': 'babel-jest', }, ```
2018-12-23 20:55:35 +00:00
"jest": "^23.6.0",
Added with-jest-typescript example (#4124) * Added with-jest-typescript example with files and readme * Updated package.json As per the comment, updated the package.json so the info is same as in other examples. * Proper name in package.json
2018-04-13 14:53:59 +00:00
"react-addons-test-utils": "^15.6.2",
"react-test-renderer": "^16.2.0",
"typescript": "^2.7.2"
}
}
Reference in a new issue Copy permalink