You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
vitest/browser + nuxt | Failed to resolve entry for package "@sentry/nuxt" #18070
3:29:10 PM [vite] Internal server error: Failed to resolve entry for package "@sentry/nuxt". The package may have incorrect main/module/exports specified in its package.json: No known conditions for "." specifier in "@sentry/nuxt" package
Plugin: vite:import-analysis
File: examples/app-vitest-browser/sentry.client.config.ts:1:24
1 | import * as Sentry from "@sentry/nuxt";
| ^
2 | Sentry.init({
3 | // If set up, you can use your runtime config here
changed the title [-]vitest nuxt | `Failed to resolve entry for package "@sentry/nuxt"`[/-][+]vitest + nuxt | `Failed to resolve entry for package "@sentry/nuxt"`[/+]on Oct 31, 2025
I created a PR to add a default fallback in general, but it happens because environment is set to nuxt, is this a convention to expect in the Nuxt ecosystem?
changed the title [-]vitest + nuxt | `Failed to resolve entry for package "@sentry/nuxt"`[/-][+]vitest/browser + nuxt | `Failed to resolve entry for package "@sentry/nuxt"`[/+]on Nov 3, 2025
Activity
linear commentedon Oct 31, 2025
JS-1104
[-]vitest nuxt | `Failed to resolve entry for package "@sentry/nuxt"`[/-][+]vitest + nuxt | `Failed to resolve entry for package "@sentry/nuxt"`[/+]logaretm commentedon Nov 3, 2025
I created a PR to add a default fallback in general, but it happens because
environmentis set tonuxt, is this a convention to expect in the Nuxt ecosystem?OrbisK commentedon Nov 3, 2025
Yes, it is pretty common to use the nuxt runtime env for component testing. https://nuxt.com/docs/4.x/getting-started/testing#using-a-nuxt-runtime-environment
[-]vitest + nuxt | `Failed to resolve entry for package "@sentry/nuxt"`[/-][+]vitest/browser + nuxt | `Failed to resolve entry for package "@sentry/nuxt"`[/+]fix(nuxt): Added top-level fallback exports (#18083)
github-actions commentedon Nov 5, 2025
A PR closing this issue has just been released 🚀
This issue was referenced by PR #18083, which was included in the 10.23.0 release.