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
gpu_compatibility
infrastructure-gpu-compatibility-when-running-gemma-2-with-flashinfer-on-an-nvidia--6f3f1857
Tier 1 · 70%
service_resilienceinfrastructure-service-resilience-clickhouse-is-unavailable-causing-trace-ingestion--59b25f81
Tier 1 · 70%
mypy_compatibilityinfrastructure-mypy-compatibility-mypy-reports-has-no-attribute-errors-on-trainer-or-fd61fa5e
Tier 1 · 70%
repo_structureinfrastructure-repo-structure-cloning-a-repository-fails-on-windows-because-a-di-c0798793
Tier 1 · 70%
provider_migrationinfrastructure-provider-migration-need-to-migrate-existing-openai-anthropic-or-googl-3e72218b
Tier 1 · 70%
streamable_http_race_conditioninfrastructure-streamable-http-race-closedresourceerror-in-handle-stateless-request-wh-6a21a92a
Tier 1 · 70%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.