Vite "Failed to resolve entry for package" (exports map) in CI

Vite tried to resolve a package entry but its exports field (or missing main/module) did not advertise a usable entry point for the conditions Vite requested. The build aborts during dependency resolution.

What this error means

A vite build fails with "Failed to resolve entry for package" and a hint that the package may have an incorrect main/module/exports. The package installed fine; only resolution fails.

node

error during build:
Failed to resolve entry for package "some-lib". The package may have
incorrect main/module/exports specified in its package.json.

Common causes

The exports map lacks the requested condition

Modern packages gate entries behind exports conditions (import/require/default). If none matches what Vite asks for, there is no entry to resolve.

A bad or missing main/module field

An older package points main at a file that does not exist, or ships ESM with no module/exports, leaving Vite nothing valid to load.

How to fix it

Upgrade or pin a version with a correct exports map

Most cases are a known bug in a specific release. Upgrade the dependency or pin to a version with a valid exports field.

Check the package CHANGELOG/issues for an exports fix.
Upgrade: npm install some-lib@latest.
If a regression, pin to the last good version in package.json.

Add a resolve alias as a workaround

Point Vite directly at the real entry file when the package map is broken and you cannot upgrade.

vite.config.ts

// vite.config.ts
export default {
  resolve: {
    alias: { 'some-lib': 'some-lib/dist/index.js' },
  },
};

How to prevent it

Pin dependency versions so a published exports-map regression cannot break CI unexpectedly.
Test production builds in CI, not only the dev server, since resolution differs.
Prefer packages with well-formed exports conditions.