fix(nuxt): Windows file:// for import-in-the-middle hook and isAbsolute for C:\ by halillusion · Pull Request #23653 · getsentry/sentry-javascript

halillusion · 2026-08-26T12:36:28Z

tests added if needed
yarn lint passes
no related issue, auto-link is fine

Windows fix for Nuxt dev on Node 24.

On Windows npm run dev was failing with ERR_UNSUPPORTED_ESM_URL_SCHEME / Received protocol 'c:' because .nuxt/dev/index.mjs generated import 'C:\...' instead of file:///C:/.... Same isExternal check in rollup.module.config.mjs treated C:\ as external and broke the build.

Changed addServerConfig.ts (and the solidstart copy) to emit pathToFileURL(...).href and fixed isExternal to use isAbsolute() so Windows absolute paths work. Also handles POSIX fine.

Verified with yarn nx run @sentry/nuxt:build:dev -> now passes, and pathToFileURL gives file:///C:/... on Windows.

Closes #XXXX

…njection and entry file wrapping

On Windows fileURLToPath returns backslash paths (C:\...), so includes('/sentry.server.config') never matched. The config was not marked moduleSideEffects:true and could be tree-shaken, disabling Sentry server init. Normalized paths to forward slashes before the check and keep file:// emission for Node ESM while mapping file:// back to filesystem paths for Rollup. Fixes handling for both packages/nuxt and packages/solidstart wrapEntry plugins.

s1gr1d · 2026-08-26T13:28:00Z

 // Anything that isn't a relative path is provided by the consuming app or Node at runtime
 // (this covers `@sentry/*`, `nuxt/app`, `#imports`, node builtins), so it stays external.
-const isExternal = id => !id.startsWith('.') && !id.startsWith('/') && !id.startsWith('\0');
+const isExternal = id => !id.startsWith('.') && !isAbsolute(id) && !id.startsWith('\0');


Good catch!

s1gr1d · 2026-08-26T13:36:53Z

 return {
 name: 'sentry-wrap-entry-with-dynamic-import',
 async resolveId(source, importer, options) {
- if (source.includes(`/${SERVER_CONFIG_FILENAME}`)) {


You could probably just do this:
if (path.basename(source).startsWith(SERVER_CONFIG_FILENAME)) {
This does not include the forward slash anymore.

…eview (isAbsolute/basename).

…try plugin

github-actions · 2026-08-31T10:17:22Z

👋 @mydea, @s1gr1d — Please review this PR when you get a chance!

s1gr1d

Some general comments:

there are no new tests. Would be great to add unit tests for the new branches in the rollup plugins
formatting fails: run yarn format in the root

s1gr1d · 2026-08-31T15:33:53Z

+ let normalizedSource = source;
+ if (source.startsWith('file://')) {
+ try {
+ normalizedSource = fileURLToPath(source);
+ } catch {
+ return null;
+ }
+ }


This part is very much the same from the part below where source.startsWith( is checked again.
You could write a util function, e.g.
/** * `load()` emits `file://` specifiers because Node's ESM loader rejects bare Windows * paths (`ERR_UNSUPPORTED_ESM_URL_SCHEME`), but Rollup's resolver only understands * filesystem paths. Returns `undefined` for a malformed `file://` URL. */exportfunctiontoResolvablePath(source: string): {path: string;wasFileUrl: boolean}|undefined{if(!source.startsWith('file://')){return{path: source,wasFileUrl: false};}try{return{path: fileURLToPath(source),wasFileUrl: true};}catch{returnundefined;}}

s1gr1d · 2026-08-31T15:36:31Z

+ if (source.startsWith('file://')) {
+ const resolved = await this.resolve(normalizedSource, importer, { ...options, isEntry: false });
+ if (resolved) return resolved;
+ return { id: normalizedSource };
+ }


With the helper util I mentioned above, you could do this here:
if(wasFileUrl){// other code}

On Windows, Node's ESM loader rejects bare absolute paths (C:\...) with ERR_UNSUPPORTED_ESM_URL_SCHEME (protocol 'c:'). Emit file:// URLs from wrapEntryWithDynamicImport load hook for the Sentry server config, wrapped entry point, and serverless re-exports. In resolveId, normalize incoming file:// URLs back to filesystem paths via toResolvablePath() and forward them with isEntry: false to prevent double-wrapping. Applied symmetrically to @sentry/nuxt and @sentry/solidstart, with unit tests covering URL normalization and entry resolution.

…tensions

s1gr1d · 2026-09-01T12:04:20Z

Please merge in the changes from develop and resolve the conflicts.

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 28367c0. Configure here.}

s1gr1d · 2026-09-02T13:05:43Z

Some tests are still failing:

 ❯ test/vite/addServerConfig.test.ts (18 tests | 2 failed) 38ms
✓ toResolvablePath > passes through non-file specifiers 5ms
✓ toResolvablePath > converts file:// URLs to filesystem paths 0ms
× toResolvablePath > returns undefined for malformed file:// URLs 15ms
→ expected { path: '/', wasFileUrl: true } to be undefined
✓ wrapEntryWithDynamicImport > emits file:// URLs from load() so Node resolves them on Windows 1ms
✓ wrapEntryWithDynamicImport > uses file:// URLs for re-exported functions 1ms
✓ wrapEntryWithDynamicImport > resolves a file:// config URL to a filesystem path with moduleSideEffects 1ms
✓ wrapEntryWithDynamicImport > resolves a plain config path without converting it 0ms
✓ wrapEntryWithDynamicImport > does not mark backup or test config files as the Sentry server config 2ms
✓ wrapEntryWithDynamicImport > resolves file:// entry specifiers without re-entering the entry branch 1ms
× wrapEntryWithDynamicImport > returns null for malformed file:// URLs 2ms
→ expected { id: '/' } to be null

… in resolve

halillusion · 2026-09-02T13:39:11Z

Synced with develop and addressed the latest feedback:

POSIX file:// handling: Fixed toResolvablePath returning { path: '/', wasFileUrl: true } on Linux for malformed file:// URLs.
Resolver slash prefix: Removed leading slashes from createResolver.resolve() in addServerConfig.ts to ensure clean Windows absolute path resolution.
Cross-platform tests: All unit tests in @sentry/nuxt (17 files, 331 tests) now pass cleanly.

s1gr1d · 2026-09-03T09:05:46Z

I merged develop into your branch to see if CI is green - it works now. Just one little comment as there's a change in the claude file.

github-actions · 2026-09-03T10:16:42Z

👋 @mydea — Please review this PR when you get a chance!

halillusion · 2026-08-26T12:36:28Z

tests added if needed
yarn lint passes
no related issue, auto-link is fine

Windows fix for Nuxt dev on Node 24.

On Windows npm run dev was failing with ERR_UNSUPPORTED_ESM_URL_SCHEME / Received protocol 'c:' because .nuxt/dev/index.mjs generated import 'C:\...' instead of file:///C:/.... Same isExternal check in rollup.module.config.mjs treated C:\ as external and broke the build.

Changed addServerConfig.ts (and the solidstart copy) to emit pathToFileURL(...).href and fixed isExternal to use isAbsolute() so Windows absolute paths work. Also handles POSIX fine.

Verified with yarn nx run @sentry/nuxt:build:dev -> now passes, and pathToFileURL gives file:///C:/... on Windows.

Closes #XXXX

…njection and entry file wrapping

On Windows fileURLToPath returns backslash paths (C:\...), so includes('/sentry.server.config') never matched. The config was not marked moduleSideEffects:true and could be tree-shaken, disabling Sentry server init. Normalized paths to forward slashes before the check and keep file:// emission for Node ESM while mapping file:// back to filesystem paths for Rollup. Fixes handling for both packages/nuxt and packages/solidstart wrapEntry plugins.

s1gr1d · 2026-08-26T13:28:00Z

 // Anything that isn't a relative path is provided by the consuming app or Node at runtime
 // (this covers `@sentry/*`, `nuxt/app`, `#imports`, node builtins), so it stays external.
-const isExternal = id => !id.startsWith('.') && !id.startsWith('/') && !id.startsWith('\0');
+const isExternal = id => !id.startsWith('.') && !isAbsolute(id) && !id.startsWith('\0');


Good catch!

s1gr1d · 2026-08-26T13:36:53Z

 return {
 name: 'sentry-wrap-entry-with-dynamic-import',
 async resolveId(source, importer, options) {
- if (source.includes(`/${SERVER_CONFIG_FILENAME}`)) {


You could probably just do this:
if (path.basename(source).startsWith(SERVER_CONFIG_FILENAME)) {
This does not include the forward slash anymore.

…eview (isAbsolute/basename).

…try plugin

github-actions · 2026-08-31T10:17:22Z

👋 @mydea, @s1gr1d — Please review this PR when you get a chance!

s1gr1d

Some general comments:

there are no new tests. Would be great to add unit tests for the new branches in the rollup plugins
formatting fails: run yarn format in the root

s1gr1d · 2026-08-31T15:33:53Z

+ let normalizedSource = source;
+ if (source.startsWith('file://')) {
+ try {
+ normalizedSource = fileURLToPath(source);
+ } catch {
+ return null;
+ }
+ }


This part is very much the same from the part below where source.startsWith( is checked again.
You could write a util function, e.g.
/** * `load()` emits `file://` specifiers because Node's ESM loader rejects bare Windows * paths (`ERR_UNSUPPORTED_ESM_URL_SCHEME`), but Rollup's resolver only understands * filesystem paths. Returns `undefined` for a malformed `file://` URL. */exportfunctiontoResolvablePath(source: string): {path: string;wasFileUrl: boolean}|undefined{if(!source.startsWith('file://')){return{path: source,wasFileUrl: false};}try{return{path: fileURLToPath(source),wasFileUrl: true};}catch{returnundefined;}}

s1gr1d · 2026-08-31T15:36:31Z

+ if (source.startsWith('file://')) {
+ const resolved = await this.resolve(normalizedSource, importer, { ...options, isEntry: false });
+ if (resolved) return resolved;
+ return { id: normalizedSource };
+ }


With the helper util I mentioned above, you could do this here:
if(wasFileUrl){// other code}

On Windows, Node's ESM loader rejects bare absolute paths (C:\...) with ERR_UNSUPPORTED_ESM_URL_SCHEME (protocol 'c:'). Emit file:// URLs from wrapEntryWithDynamicImport load hook for the Sentry server config, wrapped entry point, and serverless re-exports. In resolveId, normalize incoming file:// URLs back to filesystem paths via toResolvablePath() and forward them with isEntry: false to prevent double-wrapping. Applied symmetrically to @sentry/nuxt and @sentry/solidstart, with unit tests covering URL normalization and entry resolution.

…tensions

s1gr1d · 2026-09-01T12:04:20Z

Please merge in the changes from develop and resolve the conflicts.

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 28367c0. Configure here.}

s1gr1d · 2026-09-02T13:05:43Z

Some tests are still failing:

 ❯ test/vite/addServerConfig.test.ts (18 tests | 2 failed) 38ms
✓ toResolvablePath > passes through non-file specifiers 5ms
✓ toResolvablePath > converts file:// URLs to filesystem paths 0ms
× toResolvablePath > returns undefined for malformed file:// URLs 15ms
→ expected { path: '/', wasFileUrl: true } to be undefined
✓ wrapEntryWithDynamicImport > emits file:// URLs from load() so Node resolves them on Windows 1ms
✓ wrapEntryWithDynamicImport > uses file:// URLs for re-exported functions 1ms
✓ wrapEntryWithDynamicImport > resolves a file:// config URL to a filesystem path with moduleSideEffects 1ms
✓ wrapEntryWithDynamicImport > resolves a plain config path without converting it 0ms
✓ wrapEntryWithDynamicImport > does not mark backup or test config files as the Sentry server config 2ms
✓ wrapEntryWithDynamicImport > resolves file:// entry specifiers without re-entering the entry branch 1ms
× wrapEntryWithDynamicImport > returns null for malformed file:// URLs 2ms
→ expected { id: '/' } to be null

… in resolve

halillusion · 2026-09-02T13:39:11Z

Synced with develop and addressed the latest feedback:

POSIX file:// handling: Fixed toResolvablePath returning { path: '/', wasFileUrl: true } on Linux for malformed file:// URLs.
Resolver slash prefix: Removed leading slashes from createResolver.resolve() in addServerConfig.ts to ensure clean Windows absolute path resolution.
Cross-platform tests: All unit tests in @sentry/nuxt (17 files, 331 tests) now pass cleanly.

s1gr1d · 2026-09-03T09:05:46Z

I merged develop into your branch to see if CI is green - it works now. Just one little comment as there's a change in the claude file.

github-actions · 2026-09-03T10:16:42Z

👋 @mydea — Please review this PR when you get a chance!

halillusion · 2026-08-26T12:36:28Z

tests added if needed
yarn lint passes
no related issue, auto-link is fine

Windows fix for Nuxt dev on Node 24.

On Windows npm run dev was failing with ERR_UNSUPPORTED_ESM_URL_SCHEME / Received protocol 'c:' because .nuxt/dev/index.mjs generated import 'C:\...' instead of file:///C:/.... Same isExternal check in rollup.module.config.mjs treated C:\ as external and broke the build.

Changed addServerConfig.ts (and the solidstart copy) to emit pathToFileURL(...).href and fixed isExternal to use isAbsolute() so Windows absolute paths work. Also handles POSIX fine.

Verified with yarn nx run @sentry/nuxt:build:dev -> now passes, and pathToFileURL gives file:///C:/... on Windows.

Closes #XXXX

…njection and entry file wrapping

On Windows fileURLToPath returns backslash paths (C:\...), so includes('/sentry.server.config') never matched. The config was not marked moduleSideEffects:true and could be tree-shaken, disabling Sentry server init. Normalized paths to forward slashes before the check and keep file:// emission for Node ESM while mapping file:// back to filesystem paths for Rollup. Fixes handling for both packages/nuxt and packages/solidstart wrapEntry plugins.

s1gr1d · 2026-08-26T13:28:00Z

 // Anything that isn't a relative path is provided by the consuming app or Node at runtime
 // (this covers `@sentry/*`, `nuxt/app`, `#imports`, node builtins), so it stays external.
-const isExternal = id => !id.startsWith('.') && !id.startsWith('/') && !id.startsWith('\0');
+const isExternal = id => !id.startsWith('.') && !isAbsolute(id) && !id.startsWith('\0');


Good catch!

s1gr1d · 2026-08-26T13:36:53Z

 return {
 name: 'sentry-wrap-entry-with-dynamic-import',
 async resolveId(source, importer, options) {
- if (source.includes(`/${SERVER_CONFIG_FILENAME}`)) {


You could probably just do this:
if (path.basename(source).startsWith(SERVER_CONFIG_FILENAME)) {
This does not include the forward slash anymore.

…eview (isAbsolute/basename).

…try plugin

github-actions · 2026-08-31T10:17:22Z

👋 @mydea, @s1gr1d — Please review this PR when you get a chance!

s1gr1d

Some general comments:

there are no new tests. Would be great to add unit tests for the new branches in the rollup plugins
formatting fails: run yarn format in the root

s1gr1d · 2026-08-31T15:33:53Z

+ let normalizedSource = source;
+ if (source.startsWith('file://')) {
+ try {
+ normalizedSource = fileURLToPath(source);
+ } catch {
+ return null;
+ }
+ }


This part is very much the same from the part below where source.startsWith( is checked again.
You could write a util function, e.g.
/** * `load()` emits `file://` specifiers because Node's ESM loader rejects bare Windows * paths (`ERR_UNSUPPORTED_ESM_URL_SCHEME`), but Rollup's resolver only understands * filesystem paths. Returns `undefined` for a malformed `file://` URL. */exportfunctiontoResolvablePath(source: string): {path: string;wasFileUrl: boolean}|undefined{if(!source.startsWith('file://')){return{path: source,wasFileUrl: false};}try{return{path: fileURLToPath(source),wasFileUrl: true};}catch{returnundefined;}}

s1gr1d · 2026-08-31T15:36:31Z

+ if (source.startsWith('file://')) {
+ const resolved = await this.resolve(normalizedSource, importer, { ...options, isEntry: false });
+ if (resolved) return resolved;
+ return { id: normalizedSource };
+ }


With the helper util I mentioned above, you could do this here:
if(wasFileUrl){// other code}

On Windows, Node's ESM loader rejects bare absolute paths (C:\...) with ERR_UNSUPPORTED_ESM_URL_SCHEME (protocol 'c:'). Emit file:// URLs from wrapEntryWithDynamicImport load hook for the Sentry server config, wrapped entry point, and serverless re-exports. In resolveId, normalize incoming file:// URLs back to filesystem paths via toResolvablePath() and forward them with isEntry: false to prevent double-wrapping. Applied symmetrically to @sentry/nuxt and @sentry/solidstart, with unit tests covering URL normalization and entry resolution.

…tensions

s1gr1d · 2026-09-01T12:04:20Z

Please merge in the changes from develop and resolve the conflicts.

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 28367c0. Configure here.}

s1gr1d · 2026-09-02T13:05:43Z

Some tests are still failing:

 ❯ test/vite/addServerConfig.test.ts (18 tests | 2 failed) 38ms
✓ toResolvablePath > passes through non-file specifiers 5ms
✓ toResolvablePath > converts file:// URLs to filesystem paths 0ms
× toResolvablePath > returns undefined for malformed file:// URLs 15ms
→ expected { path: '/', wasFileUrl: true } to be undefined
✓ wrapEntryWithDynamicImport > emits file:// URLs from load() so Node resolves them on Windows 1ms
✓ wrapEntryWithDynamicImport > uses file:// URLs for re-exported functions 1ms
✓ wrapEntryWithDynamicImport > resolves a file:// config URL to a filesystem path with moduleSideEffects 1ms
✓ wrapEntryWithDynamicImport > resolves a plain config path without converting it 0ms
✓ wrapEntryWithDynamicImport > does not mark backup or test config files as the Sentry server config 2ms
✓ wrapEntryWithDynamicImport > resolves file:// entry specifiers without re-entering the entry branch 1ms
× wrapEntryWithDynamicImport > returns null for malformed file:// URLs 2ms
→ expected { id: '/' } to be null

… in resolve

halillusion · 2026-09-02T13:39:11Z

Synced with develop and addressed the latest feedback:

POSIX file:// handling: Fixed toResolvablePath returning { path: '/', wasFileUrl: true } on Linux for malformed file:// URLs.
Resolver slash prefix: Removed leading slashes from createResolver.resolve() in addServerConfig.ts to ensure clean Windows absolute path resolution.
Cross-platform tests: All unit tests in @sentry/nuxt (17 files, 331 tests) now pass cleanly.

s1gr1d · 2026-09-03T09:05:46Z

I merged develop into your branch to see if CI is green - it works now. Just one little comment as there's a change in the claude file.

github-actions · 2026-09-03T10:16:42Z

👋 @mydea — Please review this PR when you get a chance!

halillusion · 2026-08-26T12:36:28Z

tests added if needed
yarn lint passes
no related issue, auto-link is fine

Windows fix for Nuxt dev on Node 24.

On Windows npm run dev was failing with ERR_UNSUPPORTED_ESM_URL_SCHEME / Received protocol 'c:' because .nuxt/dev/index.mjs generated import 'C:\...' instead of file:///C:/.... Same isExternal check in rollup.module.config.mjs treated C:\ as external and broke the build.

Changed addServerConfig.ts (and the solidstart copy) to emit pathToFileURL(...).href and fixed isExternal to use isAbsolute() so Windows absolute paths work. Also handles POSIX fine.

Verified with yarn nx run @sentry/nuxt:build:dev -> now passes, and pathToFileURL gives file:///C:/... on Windows.

Closes #XXXX

…njection and entry file wrapping

On Windows fileURLToPath returns backslash paths (C:\...), so includes('/sentry.server.config') never matched. The config was not marked moduleSideEffects:true and could be tree-shaken, disabling Sentry server init. Normalized paths to forward slashes before the check and keep file:// emission for Node ESM while mapping file:// back to filesystem paths for Rollup. Fixes handling for both packages/nuxt and packages/solidstart wrapEntry plugins.

s1gr1d · 2026-08-26T13:28:00Z

 // Anything that isn't a relative path is provided by the consuming app or Node at runtime
 // (this covers `@sentry/*`, `nuxt/app`, `#imports`, node builtins), so it stays external.
-const isExternal = id => !id.startsWith('.') && !id.startsWith('/') && !id.startsWith('\0');
+const isExternal = id => !id.startsWith('.') && !isAbsolute(id) && !id.startsWith('\0');


Good catch!

s1gr1d · 2026-08-26T13:36:53Z

 return {
 name: 'sentry-wrap-entry-with-dynamic-import',
 async resolveId(source, importer, options) {
- if (source.includes(`/${SERVER_CONFIG_FILENAME}`)) {


You could probably just do this:
if (path.basename(source).startsWith(SERVER_CONFIG_FILENAME)) {
This does not include the forward slash anymore.

…eview (isAbsolute/basename).

…try plugin

github-actions · 2026-08-31T10:17:22Z

👋 @mydea, @s1gr1d — Please review this PR when you get a chance!

s1gr1d

Some general comments:

there are no new tests. Would be great to add unit tests for the new branches in the rollup plugins
formatting fails: run yarn format in the root

s1gr1d · 2026-08-31T15:33:53Z

+ let normalizedSource = source;
+ if (source.startsWith('file://')) {
+ try {
+ normalizedSource = fileURLToPath(source);
+ } catch {
+ return null;
+ }
+ }


This part is very much the same from the part below where source.startsWith( is checked again.
You could write a util function, e.g.
/** * `load()` emits `file://` specifiers because Node's ESM loader rejects bare Windows * paths (`ERR_UNSUPPORTED_ESM_URL_SCHEME`), but Rollup's resolver only understands * filesystem paths. Returns `undefined` for a malformed `file://` URL. */exportfunctiontoResolvablePath(source: string): {path: string;wasFileUrl: boolean}|undefined{if(!source.startsWith('file://')){return{path: source,wasFileUrl: false};}try{return{path: fileURLToPath(source),wasFileUrl: true};}catch{returnundefined;}}

s1gr1d · 2026-08-31T15:36:31Z

+ if (source.startsWith('file://')) {
+ const resolved = await this.resolve(normalizedSource, importer, { ...options, isEntry: false });
+ if (resolved) return resolved;
+ return { id: normalizedSource };
+ }


With the helper util I mentioned above, you could do this here:
if(wasFileUrl){// other code}

On Windows, Node's ESM loader rejects bare absolute paths (C:\...) with ERR_UNSUPPORTED_ESM_URL_SCHEME (protocol 'c:'). Emit file:// URLs from wrapEntryWithDynamicImport load hook for the Sentry server config, wrapped entry point, and serverless re-exports. In resolveId, normalize incoming file:// URLs back to filesystem paths via toResolvablePath() and forward them with isEntry: false to prevent double-wrapping. Applied symmetrically to @sentry/nuxt and @sentry/solidstart, with unit tests covering URL normalization and entry resolution.

…tensions

s1gr1d · 2026-09-01T12:04:20Z

Please merge in the changes from develop and resolve the conflicts.

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 28367c0. Configure here.}

s1gr1d · 2026-09-02T13:05:43Z

Some tests are still failing:

 ❯ test/vite/addServerConfig.test.ts (18 tests | 2 failed) 38ms
✓ toResolvablePath > passes through non-file specifiers 5ms
✓ toResolvablePath > converts file:// URLs to filesystem paths 0ms
× toResolvablePath > returns undefined for malformed file:// URLs 15ms
→ expected { path: '/', wasFileUrl: true } to be undefined
✓ wrapEntryWithDynamicImport > emits file:// URLs from load() so Node resolves them on Windows 1ms
✓ wrapEntryWithDynamicImport > uses file:// URLs for re-exported functions 1ms
✓ wrapEntryWithDynamicImport > resolves a file:// config URL to a filesystem path with moduleSideEffects 1ms
✓ wrapEntryWithDynamicImport > resolves a plain config path without converting it 0ms
✓ wrapEntryWithDynamicImport > does not mark backup or test config files as the Sentry server config 2ms
✓ wrapEntryWithDynamicImport > resolves file:// entry specifiers without re-entering the entry branch 1ms
× wrapEntryWithDynamicImport > returns null for malformed file:// URLs 2ms
→ expected { id: '/' } to be null

… in resolve

halillusion · 2026-09-02T13:39:11Z

Synced with develop and addressed the latest feedback:

POSIX file:// handling: Fixed toResolvablePath returning { path: '/', wasFileUrl: true } on Linux for malformed file:// URLs.
Resolver slash prefix: Removed leading slashes from createResolver.resolve() in addServerConfig.ts to ensure clean Windows absolute path resolution.
Cross-platform tests: All unit tests in @sentry/nuxt (17 files, 331 tests) now pass cleanly.

s1gr1d · 2026-09-03T09:05:46Z

I merged develop into your branch to see if CI is green - it works now. Just one little comment as there's a change in the claude file.

github-actions · 2026-09-03T10:16:42Z

👋 @mydea — Please review this PR when you get a chance!

halillusion · 2026-08-26T12:36:28Z

tests added if needed
yarn lint passes
no related issue, auto-link is fine

Windows fix for Nuxt dev on Node 24.

On Windows npm run dev was failing with ERR_UNSUPPORTED_ESM_URL_SCHEME / Received protocol 'c:' because .nuxt/dev/index.mjs generated import 'C:\...' instead of file:///C:/.... Same isExternal check in rollup.module.config.mjs treated C:\ as external and broke the build.

Changed addServerConfig.ts (and the solidstart copy) to emit pathToFileURL(...).href and fixed isExternal to use isAbsolute() so Windows absolute paths work. Also handles POSIX fine.

Verified with yarn nx run @sentry/nuxt:build:dev -> now passes, and pathToFileURL gives file:///C:/... on Windows.

Closes #XXXX

…njection and entry file wrapping

On Windows fileURLToPath returns backslash paths (C:\...), so includes('/sentry.server.config') never matched. The config was not marked moduleSideEffects:true and could be tree-shaken, disabling Sentry server init. Normalized paths to forward slashes before the check and keep file:// emission for Node ESM while mapping file:// back to filesystem paths for Rollup. Fixes handling for both packages/nuxt and packages/solidstart wrapEntry plugins.

s1gr1d · 2026-08-26T13:28:00Z

 // Anything that isn't a relative path is provided by the consuming app or Node at runtime
 // (this covers `@sentry/*`, `nuxt/app`, `#imports`, node builtins), so it stays external.
-const isExternal = id => !id.startsWith('.') && !id.startsWith('/') && !id.startsWith('\0');
+const isExternal = id => !id.startsWith('.') && !isAbsolute(id) && !id.startsWith('\0');


Good catch!

s1gr1d · 2026-08-26T13:36:53Z

 return {
 name: 'sentry-wrap-entry-with-dynamic-import',
 async resolveId(source, importer, options) {
- if (source.includes(`/${SERVER_CONFIG_FILENAME}`)) {


You could probably just do this:
if (path.basename(source).startsWith(SERVER_CONFIG_FILENAME)) {
This does not include the forward slash anymore.

…eview (isAbsolute/basename).

…try plugin

github-actions · 2026-08-31T10:17:22Z

👋 @mydea, @s1gr1d — Please review this PR when you get a chance!

s1gr1d

Some general comments:

there are no new tests. Would be great to add unit tests for the new branches in the rollup plugins
formatting fails: run yarn format in the root

s1gr1d · 2026-08-31T15:33:53Z

+ let normalizedSource = source;
+ if (source.startsWith('file://')) {
+ try {
+ normalizedSource = fileURLToPath(source);
+ } catch {
+ return null;
+ }
+ }


This part is very much the same from the part below where source.startsWith( is checked again.
You could write a util function, e.g.
/** * `load()` emits `file://` specifiers because Node's ESM loader rejects bare Windows * paths (`ERR_UNSUPPORTED_ESM_URL_SCHEME`), but Rollup's resolver only understands * filesystem paths. Returns `undefined` for a malformed `file://` URL. */exportfunctiontoResolvablePath(source: string): {path: string;wasFileUrl: boolean}|undefined{if(!source.startsWith('file://')){return{path: source,wasFileUrl: false};}try{return{path: fileURLToPath(source),wasFileUrl: true};}catch{returnundefined;}}

s1gr1d · 2026-08-31T15:36:31Z

+ if (source.startsWith('file://')) {
+ const resolved = await this.resolve(normalizedSource, importer, { ...options, isEntry: false });
+ if (resolved) return resolved;
+ return { id: normalizedSource };
+ }


With the helper util I mentioned above, you could do this here:
if(wasFileUrl){// other code}

On Windows, Node's ESM loader rejects bare absolute paths (C:\...) with ERR_UNSUPPORTED_ESM_URL_SCHEME (protocol 'c:'). Emit file:// URLs from wrapEntryWithDynamicImport load hook for the Sentry server config, wrapped entry point, and serverless re-exports. In resolveId, normalize incoming file:// URLs back to filesystem paths via toResolvablePath() and forward them with isEntry: false to prevent double-wrapping. Applied symmetrically to @sentry/nuxt and @sentry/solidstart, with unit tests covering URL normalization and entry resolution.

…tensions

s1gr1d · 2026-09-01T12:04:20Z

Please merge in the changes from develop and resolve the conflicts.

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 28367c0. Configure here.}

s1gr1d · 2026-09-02T13:05:43Z

Some tests are still failing:

 ❯ test/vite/addServerConfig.test.ts (18 tests | 2 failed) 38ms
✓ toResolvablePath > passes through non-file specifiers 5ms
✓ toResolvablePath > converts file:// URLs to filesystem paths 0ms
× toResolvablePath > returns undefined for malformed file:// URLs 15ms
→ expected { path: '/', wasFileUrl: true } to be undefined
✓ wrapEntryWithDynamicImport > emits file:// URLs from load() so Node resolves them on Windows 1ms
✓ wrapEntryWithDynamicImport > uses file:// URLs for re-exported functions 1ms
✓ wrapEntryWithDynamicImport > resolves a file:// config URL to a filesystem path with moduleSideEffects 1ms
✓ wrapEntryWithDynamicImport > resolves a plain config path without converting it 0ms
✓ wrapEntryWithDynamicImport > does not mark backup or test config files as the Sentry server config 2ms
✓ wrapEntryWithDynamicImport > resolves file:// entry specifiers without re-entering the entry branch 1ms
× wrapEntryWithDynamicImport > returns null for malformed file:// URLs 2ms
→ expected { id: '/' } to be null

… in resolve

halillusion · 2026-09-02T13:39:11Z

Synced with develop and addressed the latest feedback:

POSIX file:// handling: Fixed toResolvablePath returning { path: '/', wasFileUrl: true } on Linux for malformed file:// URLs.
Resolver slash prefix: Removed leading slashes from createResolver.resolve() in addServerConfig.ts to ensure clean Windows absolute path resolution.
Cross-platform tests: All unit tests in @sentry/nuxt (17 files, 331 tests) now pass cleanly.

s1gr1d · 2026-09-03T09:05:46Z

I merged develop into your branch to see if CI is green - it works now. Just one little comment as there's a change in the claude file.

github-actions · 2026-09-03T10:16:42Z

👋 @mydea — Please review this PR when you get a chance!

halillusion · 2026-08-26T12:36:28Z

tests added if needed
yarn lint passes
no related issue, auto-link is fine

Windows fix for Nuxt dev on Node 24.

On Windows npm run dev was failing with ERR_UNSUPPORTED_ESM_URL_SCHEME / Received protocol 'c:' because .nuxt/dev/index.mjs generated import 'C:\...' instead of file:///C:/.... Same isExternal check in rollup.module.config.mjs treated C:\ as external and broke the build.

Changed addServerConfig.ts (and the solidstart copy) to emit pathToFileURL(...).href and fixed isExternal to use isAbsolute() so Windows absolute paths work. Also handles POSIX fine.

Verified with yarn nx run @sentry/nuxt:build:dev -> now passes, and pathToFileURL gives file:///C:/... on Windows.

Closes #XXXX

…njection and entry file wrapping

On Windows fileURLToPath returns backslash paths (C:\...), so includes('/sentry.server.config') never matched. The config was not marked moduleSideEffects:true and could be tree-shaken, disabling Sentry server init. Normalized paths to forward slashes before the check and keep file:// emission for Node ESM while mapping file:// back to filesystem paths for Rollup. Fixes handling for both packages/nuxt and packages/solidstart wrapEntry plugins.

s1gr1d · 2026-08-26T13:28:00Z

 // Anything that isn't a relative path is provided by the consuming app or Node at runtime
 // (this covers `@sentry/*`, `nuxt/app`, `#imports`, node builtins), so it stays external.
-const isExternal = id => !id.startsWith('.') && !id.startsWith('/') && !id.startsWith('\0');
+const isExternal = id => !id.startsWith('.') && !isAbsolute(id) && !id.startsWith('\0');


Good catch!

s1gr1d · 2026-08-26T13:36:53Z

 return {
 name: 'sentry-wrap-entry-with-dynamic-import',
 async resolveId(source, importer, options) {
- if (source.includes(`/${SERVER_CONFIG_FILENAME}`)) {


You could probably just do this:
if (path.basename(source).startsWith(SERVER_CONFIG_FILENAME)) {
This does not include the forward slash anymore.

…eview (isAbsolute/basename).

…try plugin

github-actions · 2026-08-31T10:17:22Z

👋 @mydea, @s1gr1d — Please review this PR when you get a chance!

s1gr1d

Some general comments:

there are no new tests. Would be great to add unit tests for the new branches in the rollup plugins
formatting fails: run yarn format in the root

s1gr1d · 2026-08-31T15:33:53Z

+ let normalizedSource = source;
+ if (source.startsWith('file://')) {
+ try {
+ normalizedSource = fileURLToPath(source);
+ } catch {
+ return null;
+ }
+ }


This part is very much the same from the part below where source.startsWith( is checked again.
You could write a util function, e.g.
/** * `load()` emits `file://` specifiers because Node's ESM loader rejects bare Windows * paths (`ERR_UNSUPPORTED_ESM_URL_SCHEME`), but Rollup's resolver only understands * filesystem paths. Returns `undefined` for a malformed `file://` URL. */exportfunctiontoResolvablePath(source: string): {path: string;wasFileUrl: boolean}|undefined{if(!source.startsWith('file://')){return{path: source,wasFileUrl: false};}try{return{path: fileURLToPath(source),wasFileUrl: true};}catch{returnundefined;}}

s1gr1d · 2026-08-31T15:36:31Z

+ if (source.startsWith('file://')) {
+ const resolved = await this.resolve(normalizedSource, importer, { ...options, isEntry: false });
+ if (resolved) return resolved;
+ return { id: normalizedSource };
+ }


With the helper util I mentioned above, you could do this here:
if(wasFileUrl){// other code}

On Windows, Node's ESM loader rejects bare absolute paths (C:\...) with ERR_UNSUPPORTED_ESM_URL_SCHEME (protocol 'c:'). Emit file:// URLs from wrapEntryWithDynamicImport load hook for the Sentry server config, wrapped entry point, and serverless re-exports. In resolveId, normalize incoming file:// URLs back to filesystem paths via toResolvablePath() and forward them with isEntry: false to prevent double-wrapping. Applied symmetrically to @sentry/nuxt and @sentry/solidstart, with unit tests covering URL normalization and entry resolution.

…tensions

s1gr1d · 2026-09-01T12:04:20Z

Please merge in the changes from develop and resolve the conflicts.

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 28367c0. Configure here.}

s1gr1d · 2026-09-02T13:05:43Z

Some tests are still failing:

 ❯ test/vite/addServerConfig.test.ts (18 tests | 2 failed) 38ms
✓ toResolvablePath > passes through non-file specifiers 5ms
✓ toResolvablePath > converts file:// URLs to filesystem paths 0ms
× toResolvablePath > returns undefined for malformed file:// URLs 15ms
→ expected { path: '/', wasFileUrl: true } to be undefined
✓ wrapEntryWithDynamicImport > emits file:// URLs from load() so Node resolves them on Windows 1ms
✓ wrapEntryWithDynamicImport > uses file:// URLs for re-exported functions 1ms
✓ wrapEntryWithDynamicImport > resolves a file:// config URL to a filesystem path with moduleSideEffects 1ms
✓ wrapEntryWithDynamicImport > resolves a plain config path without converting it 0ms
✓ wrapEntryWithDynamicImport > does not mark backup or test config files as the Sentry server config 2ms
✓ wrapEntryWithDynamicImport > resolves file:// entry specifiers without re-entering the entry branch 1ms
× wrapEntryWithDynamicImport > returns null for malformed file:// URLs 2ms
→ expected { id: '/' } to be null

… in resolve

halillusion · 2026-09-02T13:39:11Z

Synced with develop and addressed the latest feedback:

POSIX file:// handling: Fixed toResolvablePath returning { path: '/', wasFileUrl: true } on Linux for malformed file:// URLs.
Resolver slash prefix: Removed leading slashes from createResolver.resolve() in addServerConfig.ts to ensure clean Windows absolute path resolution.
Cross-platform tests: All unit tests in @sentry/nuxt (17 files, 331 tests) now pass cleanly.

s1gr1d · 2026-09-03T09:05:46Z

I merged develop into your branch to see if CI is green - it works now. Just one little comment as there's a change in the claude file.

github-actions · 2026-09-03T10:16:42Z

👋 @mydea — Please review this PR when you get a chance!

halillusion · 2026-08-26T12:36:28Z

tests added if needed
yarn lint passes
no related issue, auto-link is fine

Windows fix for Nuxt dev on Node 24.

On Windows npm run dev was failing with ERR_UNSUPPORTED_ESM_URL_SCHEME / Received protocol 'c:' because .nuxt/dev/index.mjs generated import 'C:\...' instead of file:///C:/.... Same isExternal check in rollup.module.config.mjs treated C:\ as external and broke the build.

Changed addServerConfig.ts (and the solidstart copy) to emit pathToFileURL(...).href and fixed isExternal to use isAbsolute() so Windows absolute paths work. Also handles POSIX fine.

Verified with yarn nx run @sentry/nuxt:build:dev -> now passes, and pathToFileURL gives file:///C:/... on Windows.

Closes #XXXX

…njection and entry file wrapping

On Windows fileURLToPath returns backslash paths (C:\...), so includes('/sentry.server.config') never matched. The config was not marked moduleSideEffects:true and could be tree-shaken, disabling Sentry server init. Normalized paths to forward slashes before the check and keep file:// emission for Node ESM while mapping file:// back to filesystem paths for Rollup. Fixes handling for both packages/nuxt and packages/solidstart wrapEntry plugins.

s1gr1d · 2026-08-26T13:28:00Z

 // Anything that isn't a relative path is provided by the consuming app or Node at runtime
 // (this covers `@sentry/*`, `nuxt/app`, `#imports`, node builtins), so it stays external.
-const isExternal = id => !id.startsWith('.') && !id.startsWith('/') && !id.startsWith('\0');
+const isExternal = id => !id.startsWith('.') && !isAbsolute(id) && !id.startsWith('\0');


Good catch!

s1gr1d · 2026-08-26T13:36:53Z

 return {
 name: 'sentry-wrap-entry-with-dynamic-import',
 async resolveId(source, importer, options) {
- if (source.includes(`/${SERVER_CONFIG_FILENAME}`)) {


You could probably just do this:
if (path.basename(source).startsWith(SERVER_CONFIG_FILENAME)) {
This does not include the forward slash anymore.

…eview (isAbsolute/basename).

…try plugin

github-actions · 2026-08-31T10:17:22Z

👋 @mydea, @s1gr1d — Please review this PR when you get a chance!

s1gr1d

Some general comments:

there are no new tests. Would be great to add unit tests for the new branches in the rollup plugins
formatting fails: run yarn format in the root

s1gr1d · 2026-08-31T15:33:53Z

+ let normalizedSource = source;
+ if (source.startsWith('file://')) {
+ try {
+ normalizedSource = fileURLToPath(source);
+ } catch {
+ return null;
+ }
+ }


This part is very much the same from the part below where source.startsWith( is checked again.
You could write a util function, e.g.
/** * `load()` emits `file://` specifiers because Node's ESM loader rejects bare Windows * paths (`ERR_UNSUPPORTED_ESM_URL_SCHEME`), but Rollup's resolver only understands * filesystem paths. Returns `undefined` for a malformed `file://` URL. */exportfunctiontoResolvablePath(source: string): {path: string;wasFileUrl: boolean}|undefined{if(!source.startsWith('file://')){return{path: source,wasFileUrl: false};}try{return{path: fileURLToPath(source),wasFileUrl: true};}catch{returnundefined;}}

s1gr1d · 2026-08-31T15:36:31Z

+ if (source.startsWith('file://')) {
+ const resolved = await this.resolve(normalizedSource, importer, { ...options, isEntry: false });
+ if (resolved) return resolved;
+ return { id: normalizedSource };
+ }


With the helper util I mentioned above, you could do this here:
if(wasFileUrl){// other code}

On Windows, Node's ESM loader rejects bare absolute paths (C:\...) with ERR_UNSUPPORTED_ESM_URL_SCHEME (protocol 'c:'). Emit file:// URLs from wrapEntryWithDynamicImport load hook for the Sentry server config, wrapped entry point, and serverless re-exports. In resolveId, normalize incoming file:// URLs back to filesystem paths via toResolvablePath() and forward them with isEntry: false to prevent double-wrapping. Applied symmetrically to @sentry/nuxt and @sentry/solidstart, with unit tests covering URL normalization and entry resolution.

…tensions

s1gr1d · 2026-09-01T12:04:20Z

Please merge in the changes from develop and resolve the conflicts.

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 28367c0. Configure here.}

s1gr1d · 2026-09-02T13:05:43Z

Some tests are still failing:

 ❯ test/vite/addServerConfig.test.ts (18 tests | 2 failed) 38ms
✓ toResolvablePath > passes through non-file specifiers 5ms
✓ toResolvablePath > converts file:// URLs to filesystem paths 0ms
× toResolvablePath > returns undefined for malformed file:// URLs 15ms
→ expected { path: '/', wasFileUrl: true } to be undefined
✓ wrapEntryWithDynamicImport > emits file:// URLs from load() so Node resolves them on Windows 1ms
✓ wrapEntryWithDynamicImport > uses file:// URLs for re-exported functions 1ms
✓ wrapEntryWithDynamicImport > resolves a file:// config URL to a filesystem path with moduleSideEffects 1ms
✓ wrapEntryWithDynamicImport > resolves a plain config path without converting it 0ms
✓ wrapEntryWithDynamicImport > does not mark backup or test config files as the Sentry server config 2ms
✓ wrapEntryWithDynamicImport > resolves file:// entry specifiers without re-entering the entry branch 1ms
× wrapEntryWithDynamicImport > returns null for malformed file:// URLs 2ms
→ expected { id: '/' } to be null

… in resolve

halillusion · 2026-09-02T13:39:11Z

Synced with develop and addressed the latest feedback:

POSIX file:// handling: Fixed toResolvablePath returning { path: '/', wasFileUrl: true } on Linux for malformed file:// URLs.
Resolver slash prefix: Removed leading slashes from createResolver.resolve() in addServerConfig.ts to ensure clean Windows absolute path resolution.
Cross-platform tests: All unit tests in @sentry/nuxt (17 files, 331 tests) now pass cleanly.

s1gr1d · 2026-09-03T09:05:46Z

I merged develop into your branch to see if CI is green - it works now. Just one little comment as there's a change in the claude file.

github-actions · 2026-09-03T10:16:42Z

👋 @mydea — Please review this PR when you get a chance!

halillusion · 2026-08-26T12:36:28Z

tests added if needed
yarn lint passes
no related issue, auto-link is fine

Windows fix for Nuxt dev on Node 24.

On Windows npm run dev was failing with ERR_UNSUPPORTED_ESM_URL_SCHEME / Received protocol 'c:' because .nuxt/dev/index.mjs generated import 'C:\...' instead of file:///C:/.... Same isExternal check in rollup.module.config.mjs treated C:\ as external and broke the build.

Changed addServerConfig.ts (and the solidstart copy) to emit pathToFileURL(...).href and fixed isExternal to use isAbsolute() so Windows absolute paths work. Also handles POSIX fine.

Verified with yarn nx run @sentry/nuxt:build:dev -> now passes, and pathToFileURL gives file:///C:/... on Windows.

Closes #XXXX

…njection and entry file wrapping

On Windows fileURLToPath returns backslash paths (C:\...), so includes('/sentry.server.config') never matched. The config was not marked moduleSideEffects:true and could be tree-shaken, disabling Sentry server init. Normalized paths to forward slashes before the check and keep file:// emission for Node ESM while mapping file:// back to filesystem paths for Rollup. Fixes handling for both packages/nuxt and packages/solidstart wrapEntry plugins.

s1gr1d · 2026-08-26T13:28:00Z

 // Anything that isn't a relative path is provided by the consuming app or Node at runtime
 // (this covers `@sentry/*`, `nuxt/app`, `#imports`, node builtins), so it stays external.
-const isExternal = id => !id.startsWith('.') && !id.startsWith('/') && !id.startsWith('\0');
+const isExternal = id => !id.startsWith('.') && !isAbsolute(id) && !id.startsWith('\0');


Good catch!

s1gr1d · 2026-08-26T13:36:53Z

 return {
 name: 'sentry-wrap-entry-with-dynamic-import',
 async resolveId(source, importer, options) {
- if (source.includes(`/${SERVER_CONFIG_FILENAME}`)) {


You could probably just do this:
if (path.basename(source).startsWith(SERVER_CONFIG_FILENAME)) {
This does not include the forward slash anymore.

…eview (isAbsolute/basename).

…try plugin

github-actions · 2026-08-31T10:17:22Z

👋 @mydea, @s1gr1d — Please review this PR when you get a chance!

s1gr1d

Some general comments:

there are no new tests. Would be great to add unit tests for the new branches in the rollup plugins
formatting fails: run yarn format in the root

s1gr1d · 2026-08-31T15:33:53Z

+ let normalizedSource = source;
+ if (source.startsWith('file://')) {
+ try {
+ normalizedSource = fileURLToPath(source);
+ } catch {
+ return null;
+ }
+ }


This part is very much the same from the part below where source.startsWith( is checked again.
You could write a util function, e.g.
/** * `load()` emits `file://` specifiers because Node's ESM loader rejects bare Windows * paths (`ERR_UNSUPPORTED_ESM_URL_SCHEME`), but Rollup's resolver only understands * filesystem paths. Returns `undefined` for a malformed `file://` URL. */exportfunctiontoResolvablePath(source: string): {path: string;wasFileUrl: boolean}|undefined{if(!source.startsWith('file://')){return{path: source,wasFileUrl: false};}try{return{path: fileURLToPath(source),wasFileUrl: true};}catch{returnundefined;}}

s1gr1d · 2026-08-31T15:36:31Z

+ if (source.startsWith('file://')) {
+ const resolved = await this.resolve(normalizedSource, importer, { ...options, isEntry: false });
+ if (resolved) return resolved;
+ return { id: normalizedSource };
+ }


With the helper util I mentioned above, you could do this here:
if(wasFileUrl){// other code}

On Windows, Node's ESM loader rejects bare absolute paths (C:\...) with ERR_UNSUPPORTED_ESM_URL_SCHEME (protocol 'c:'). Emit file:// URLs from wrapEntryWithDynamicImport load hook for the Sentry server config, wrapped entry point, and serverless re-exports. In resolveId, normalize incoming file:// URLs back to filesystem paths via toResolvablePath() and forward them with isEntry: false to prevent double-wrapping. Applied symmetrically to @sentry/nuxt and @sentry/solidstart, with unit tests covering URL normalization and entry resolution.

…tensions

s1gr1d · 2026-09-01T12:04:20Z

Please merge in the changes from develop and resolve the conflicts.

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 28367c0. Configure here.}

s1gr1d · 2026-09-02T13:05:43Z

Some tests are still failing:

 ❯ test/vite/addServerConfig.test.ts (18 tests | 2 failed) 38ms
✓ toResolvablePath > passes through non-file specifiers 5ms
✓ toResolvablePath > converts file:// URLs to filesystem paths 0ms
× toResolvablePath > returns undefined for malformed file:// URLs 15ms
→ expected { path: '/', wasFileUrl: true } to be undefined
✓ wrapEntryWithDynamicImport > emits file:// URLs from load() so Node resolves them on Windows 1ms
✓ wrapEntryWithDynamicImport > uses file:// URLs for re-exported functions 1ms
✓ wrapEntryWithDynamicImport > resolves a file:// config URL to a filesystem path with moduleSideEffects 1ms
✓ wrapEntryWithDynamicImport > resolves a plain config path without converting it 0ms
✓ wrapEntryWithDynamicImport > does not mark backup or test config files as the Sentry server config 2ms
✓ wrapEntryWithDynamicImport > resolves file:// entry specifiers without re-entering the entry branch 1ms
× wrapEntryWithDynamicImport > returns null for malformed file:// URLs 2ms
→ expected { id: '/' } to be null

… in resolve

halillusion · 2026-09-02T13:39:11Z

Synced with develop and addressed the latest feedback:

POSIX file:// handling: Fixed toResolvablePath returning { path: '/', wasFileUrl: true } on Linux for malformed file:// URLs.
Resolver slash prefix: Removed leading slashes from createResolver.resolve() in addServerConfig.ts to ensure clean Windows absolute path resolution.
Cross-platform tests: All unit tests in @sentry/nuxt (17 files, 331 tests) now pass cleanly.

s1gr1d · 2026-09-03T09:05:46Z

I merged develop into your branch to see if CI is green - it works now. Just one little comment as there's a change in the claude file.

github-actions · 2026-09-03T10:16:42Z

👋 @mydea — Please review this PR when you get a chance!

fix(nuxt): Windows file:// for import and isAbsolute for C:"
d237ce3

halillusion requested a review from a team as a code owner August 26, 2026 12:36

halillusion requested review from mydea and s1gr1d and removed request for a teamAugust 26, 2026 12:36

sentryBot reviewed Aug 26, 2026
View reviewed changes

Comment threadpackages/nuxt/src/vite/addServerConfig.ts

cursorBot reviewed Aug 26, 2026
View reviewed changes

Comment threadpackages/nuxt/src/vite/addServerConfig.ts
Comment threadpackages/nuxt/src/vite/addServerConfig.ts

fix: introduce Nitro rollup plugins for Sentry server configuration i…
837e9b5
…njection and entry file wrapping

sentryBot reviewed Aug 26, 2026
View reviewed changes

Comment threadpackages/nuxt/src/vite/addServerConfig.ts Outdated

cursorBot reviewed Aug 26, 2026
View reviewed changes

Comment threadpackages/nuxt/src/vite/addServerConfig.ts

s1gr1d reviewed Aug 26, 2026
View reviewed changes

fix: Windows dev overlay by emitting file:// URLs and fixing s1gr1d r…
e50766e
…eview (isAbsolute/basename).

halillusion requested a review from s1gr1d August 26, 2026 13:51

sentryBot reviewed Aug 26, 2026
View reviewed changes

Comment threadpackages/nuxt/src/vite/addServerConfig.ts Outdated

fix(nuxt): prevent double-wrapping of file:// specifiers in server en…
22cfd7f
…try plugin

sentryBot reviewed Aug 26, 2026
View reviewed changes

Comment threadpackages/nuxt/src/vite/addServerConfig.ts

s1gr1d reviewed Aug 31, 2026
View reviewed changes

sentryBot reviewed Aug 31, 2026
View reviewed changes

Comment threadpackages/nuxt/src/vite/addServerConfig.ts

fix(nuxt): narrow server config detection to exact match and valid ex…
886b767
…tensions

halillusion requested a review from s1gr1d August 31, 2026 17:16

halillusion added 2 commits September 2, 2026 10:48

Merge branch 'develop' into fix/nuxt-windows-file-url
a0cce99

Merge branch 'develop' into fix/nuxt-windows-file-url
28367c0

cursorBot reviewed Sep 2, 2026
View reviewed changes

Comment threadpackages/nuxt/src/vite/addServerConfig.ts

halillusion added 2 commits September 2, 2026 16:23

Merge branch 'develop' into fix/nuxt-windows-file-url
a67d220

fix(nuxt): handle POSIX file:// URL validation and drop leading slash…
9ede588
… in resolve

test(nuxt): make findDefaultSdkInitFile tests cross-platform for Windows
68327b9

Merge branch 'develop' into fix/nuxt-windows-file-url
1a36f2f

s1gr1d reviewed Sep 3, 2026
View reviewed changes

Comment threadCLAUDE.md

revert: restore CLAUDE.md symlink without trailing newline
e50d826

s1gr1d approved these changes Sep 3, 2026
View reviewed changes

s1gr1d merged commit d97a57b into getsentry:developSep 3, 2026
521 of 523 checks passed

javascript-sdk-gitflowBot mentioned this pull request Sep 3, 2026
chore: Add external contributor to CHANGELOG.md #24000
Open

chargome mentioned this pull request Sep 3, 2026
chore: Merge develop into 11.0.0-beta #24013
Closed

s1gr1d mentioned this pull request Sep 3, 2026
fix(nuxt): Windows file:// for import-in-the-middle hook and isAbsolute for C:\ #24026
Open