Error: Cannot find module '@babel/preset-env' – @babel/core resolver

Question

The goal is to ensure Babel can locate and load a preset declared in the configuration so that the transformation pipeline proceeds without aborting due to a missing‑module error.

Currently the resolver treats each preset as an independent Node module requirement; there is no standardized way for a preset to declare dependencies on other presets or plugins that must be present beforehand. This leaves an open design question about whether Babel should adopt a dependency‑declaration mechanism that could influence load order and potentially prevent missing‑module errors caused by omitted transitive dependencies.

- Should presets be allowed to list required peer presets/plugins that Babel automatically resolves before loading the preset itself?
- Would introducing a preset dependency field alter the semantics of the existing left‑to‑right plugin/preset ordering guarantee?
- How would such a mechanism interact with version resolution and lockfiles without breaking backward compatibility?

Zoha · Answer

Likely cause
The error occurs when @babel/core tries to require '@babel/preset-env' but the package is absent from the project's node_modules or cannot be resolved due to hoisting or version mismatch.
Confirmed fix

Ensure the preset is installed as a dev dependency:
# npm
npm install --save-dev @babel/preset-env
# yarn
yarn add -D @babel/preset-env
# pnpm
pnpm add -D @babel/preset-env

Verify the package exists:
ls -la node_modules/@babel/preset-env/package.json

Check that the major version matches @babel/core (both 7.x):
npm ls @babel/core @babel/preset-env

If using a monorepo or Yarn workspaces, make sure the preset is listed in the workspace's package.json so it is hoisted or linked correctly.
Clear any stale caches and reinstall if needed:
rm -rf node_modules package-lock.json yarn.lock pnpm-lock.yaml
npm install   # or yarn install / pnpm install

Test resolution:
node -e "console.log(require.resolve('@babel/preset-env'))"

Should print an absolute path ending in …/lib/index.js.

Run a quick Babel transpile to confirm:
echo "const x = () => 1;" > test.js
npx babel test.js --presets=@babel/preset-env

If output shows transformed code without error, the preset loads correctly.

Error: Cannot find module '@babel/preset-env' – @babel/core resolver

1 answer

Likely cause

Confirmed fix

Your perspective belongs here.

0 question comments