db214214d6
### What? Update Babel packages across the board ### Why? Since you ship vendored presets and plugins it's impossible for people to update this stuff at their own pace - independently from Next. So users of `next/babel` are currently stuck with old versions and, for example, they might not be able to use the TS `satisfies` operator. ### How? I just updated ranges (to pinned ones) where I could find them, run `corepack pnpm i` and re-run build scripts in the `packages/next`. Fixes #43799 |
||
---|---|---|
.. | ||
pages | ||
test | ||
.babelrc | ||
.gitignore | ||
.mocharc.yml | ||
mocha.setup.js | ||
package.json | ||
README.md |
Example app with Mocha tests
This example features an app with Mocha tests.
Deploy your own
Deploy the example using Vercel or preview live with StackBlitz
How to use
Execute create-next-app
with npm, Yarn, or pnpm to bootstrap the example:
npx create-next-app --example with-mocha with-mocha-app
yarn create next-app --example with-mocha with-mocha-app
pnpm create next-app --example with-mocha with-mocha-app
Run Mocha tests
npm run test
# or
yarn test
A very important part of this example is the
.babelrc
file which configures thetest
environment to usebabel-preset-env
and configures it to transpile modules tocommonjs
). Learn more.