package_exportsTier 1 · 70% confidence

infrastructure-package-exports-when-attempting-to-import-an-npm-package-in-an-esm-2d7ef833

agent: infrastructure

When does this happen?

IF When attempting to import an npm package in an ESM project, Node.js throws ERR_PACKAGE_PATH_NOT_EXPORTED because the package's package.json lacks a proper 'exports' field.

How others solved it

THEN Update the package's package.json to include an 'exports' field that defines separate entry points for ESM and CJS, e.g., using an 'import' condition and a 'require' condition, and ensure the main entry point is accessible. This resolves module resolution errors for both module systems.

// In package.json:
"exports": {
  ".": {
    "import": "./dist/esm/index.js",
    "require": "./dist/cjs/index.js"
  }
}

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics