rsnext/examples/with-jest-typescript/.babelrc

{
  "presets": ["next/babel"]
}
Update typescript examples to use 1.0.1 of next-typescript (#4472) * Update typescript examples to use 1.0.1 of next-typescript * Add .babelrc modifications to upgraded typescript examples 2018-05-25 11:28:35 +02:00			`{`
Update typescript examples (#7867) * Updated with-jest-typescript * Updated the mobx-state-tree-typescript example * Removed the sitemap with typescript example * Updated the with css typings example 2019-07-10 12:51:21 +02:00			`"presets": ["next/babel"]`
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 10:31:21 +02:00			`}`