Skip to content
Latchkey

Parcel "@parcel/core: Failed to resolve" - Fix Builds in CI

Parcel could not resolve an import or load a transformer plugin. As a zero-config bundler it auto-installs some tooling, but in CI (often with --no-autoinstall) a missing dependency, wrong path, or uninstalled plugin fails the build.

What this error means

The build fails with @parcel/core: Failed to resolve '<module>' from '<file>' or a transformer error naming a .parcelrc plugin. It is deterministic and points at the import or plugin.

parcel output
@parcel/core: Failed to resolve './componets/App' from './src/index.js'

  /app/src/index.js:1:17
> 1 | import App from './componets/App'
    |                 ^^^^^^^^^^^^^^^^^^

Common causes

Missing dependency or wrong path

A package not installed, or a wrong/miscased import path. CI with --no-autoinstall will not silently fetch the missing package the way local Parcel might.

Parcel plugin/transformer not installed

A .parcelrc references a transformer, optimizer, or reporter plugin that is not in package.json, so Parcel cannot load it.

How to fix it

Install dependencies and disable autoinstall in CI

Declare every dependency and plugin, and run with autoinstall off so missing deps fail loudly instead of being fetched implicitly.

Terminal
npm install <package>
npx parcel build src/index.html --no-autoinstall

Declare .parcelrc plugins

Install every plugin referenced in your Parcel config.

.parcelrc
// .parcelrc
{ "extends": "@parcel/config-default",
  "transformers": { "*.svg": ["@parcel/transformer-svg-react"] } }

How to prevent it

  • Declare all dependencies and .parcelrc plugins in package.json.
  • Build with --no-autoinstall in CI for reproducible failures.
  • Match import paths and casing to real files.

Frequently asked questions

What causes ""@parcel/core: Failed to resolve""?
A package not installed, or a wrong/miscased import path. CI with --no-autoinstall will not silently fetch the missing package the way local Parcel might.
How do I fix "@parcel/core: Failed to resolve"?
Declare every dependency and plugin, and run with autoinstall off so missing deps fail loudly instead of being fetched implicitly.

Related guides

References

Latchkey auto-heals failures like this one - detected, fixed, and retried without you. Start free → 30-day trial · No credit card