Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Node.js, PHP and APIs

Jest cannot find babel-preset-env

ErrorCannot find module 'babel-preset-env' from '/path/to/project'

Short answer

Babel 7 moved its packages to the @babel scope, so the preset is now @babel/preset-env. Replace babel-preset-env or the old env shorthand in your Babel config, and install babel-jest, @babel/core and @babel/preset-env as dev dependencies.

  • Applies to Jest 29, Babel 7, Node.js 22
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Find every place the old preset name is written.

    grep -rn "preset-env\|\"env\"" .babelrc babel.config.js package.json
  2. 2Match what you see, then jump to its fix

    1. 1Error names babel-preset-env, or suggests @babel/envThe config still names the Babel 6 presetFix
    2. 2The config is right but the preset or core cannot be resolvedThe Babel packages Jest needs are not installedFix

What does the error look like?

  • Cannot find module 'babel-preset-env' from '/path/to/project'
  • Did you mean "@babel/env"?

Cause 1 of 2

The config still names the Babel 6 preset

1Check

The Babel 7 guide moved packages to the @babel scope by replacing the babel- prefix. Shorthand still works but must keep the scope.

cat .babelrc

2Fix

Use the scoped name in presets and remove the old package.

// babel.config.js
module.exports = {
  presets: [['@babel/preset-env', {targets: {node: 'current'}}]],
};

3Verify

Run the tests again.

npx jest

Confirmed by babeljs.io

Did this fix it?

Cause 2 of 2

The Babel packages Jest needs are not installed

1Check

Jest's guide installs three packages together: babel-jest, @babel/core and @babel/preset-env.

npm ls babel-jest @babel/core @babel/preset-env

2Fix

Install them as dev dependencies.

npm install --save-dev babel-jest @babel/core @babel/preset-env

3Verify

The listing shows all three, and the tests run.

npm ls babel-jest @babel/core @babel/preset-env
npx jest

Confirmed by jestjs.io

Did this fix it?

How do I stop it coming back?

  • Copy Babel setup from the current Jest guide, not from old posts.
  • Keep Babel config in one file.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Back end

ng serve says it cannot determine the project or target

Cannot determine project for command.

The Angular CLI looked through angular.json for a project that defines the target you asked for (serve, build, test) and found none, or found several and could not pick one.

3 causes, each with a fix

Back end

ng serve cannot find the dev-server builder package

Could not find the implementation for builder @angular/build:dev-server

The builder named in angular.json (for example @angular-devkit/build-angular:dev-server) is looked up as an npm package starting from the workspace root.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.