E52F fix(nuxt): Added top-level fallback exports by logaretm · Pull Request #18083 · getsentry/sentry-javascript · GitHub
[go: up one dir, main page]

Skip to content

Conversation

@logaretm
Copy link
Collaborator
@logaretm logaretm commented Nov 3, 2025
edited
Loading

It seems that in some cases where an environment in Vite is set to something other than node or browser, it won't be able to figure out the correct import paths.

This PR ensures that when Vite (or other tools) can't determine the environment from "browser" or "node" conditions alone, then it falls back to the server bundle similar to what we do in Next.js.

In the issue's case it was set to nuxt or rather vitest-environment-nuxt which doesn't seem like a pattern to account for.

closes #18070

@linear
Copy link
linear bot commented Nov 3, 2025

cursor[bot]

This comment was marked as outdated.

@logaretm logaretm force-pushed the awad/js-1104-vitest-nuxt-failed-to-resolve-entry branch from c3165dd to 66817b6 Compare November 3, 2025 12:45
cursor[bot]

This comment was marked as outdated.

@s1gr1d s1gr1d changed the title fix(nuxt): added top-level fallback exports fix(nuxt): Added top-level fallback exports Nov 3, 2025
@logaretm logaretm merged commit b57ade1 into develop Nov 3, 2025
48 checks passed
@logaretm logaretm deleted the awad/js-1104-vitest-nuxt-failed-to-resolve-entry branch November 3, 2025 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

vitest/browser + nuxt | Failed to resolve entry for package "@sentry/nuxt"

3 participants

0