Next 13 Module build failed UnhandledSchemeError #8133

alikleit · 2023-05-16T13:51:54Z

Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

Steps to Reproduce

npx create-next-app@latest

√ What is your project named? 
√ Would you like to use TypeScript with this project? Yes
√ Would you like to use ESLint with this project?  Yes
√ Would you like to use Tailwind CSS with this project?  No
√ Would you like to use `src/` directory with this project?  Yes
√ Use App Router (recommended)?  Yes
√ Would you like to customize the default import alias? Yes
√ What import alias would you like configured? ... @/*

npx @sentry/wizard@latest -i nextjs
pnpm build

Expected Result

Build should be successfull

Actual Result

Failed to compile.

C:Users<name><path-to-project>sentry.server.config.ts
Module build failed: UnhandledSchemeError: Reading from "C:Users<name><path-to-project>sentry.server.config.ts" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "c:" URIs.

dependencies

    "@sentry/nextjs": "^7.52.1",
    "@types/node": "20.1.5",
    "@types/react": "18.2.6",
    "@types/react-dom": "18.2.4",
    "eslint": "8.40.0",
    "eslint-config-next": "13.4.2",
    "next": "13.4.2",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "typescript": "5.0.4"

Product Area

Issues

Link

No response

DSN

No response

Version

No response

The text was updated successfully, but these errors were encountered:

getsantry · 2023-05-16T13:51:58Z

Assigning to @getsentry/support for routing, due by Tuesday, May 16th at 5:00 pm (sfo). ⏲️

AbhiPrasad · 2023-05-16T14:05:26Z

Hey @alikleit, thanks for writing in! Are you running this on windows?

If you run git status after you've run npx @sentry/wizard@latest -i nextjs, what gets emitted?

Also, after you've run npx @sentry/wizard@latest -i nextjs, could you share the logs that get generated? Something that looks like so:

◇  Installed @sentry/nextjs with npm.
│
◆  Created fresh sentry.server.config.ts.
│
◆  Created fresh sentry.client.config.ts.
│
◆  Created fresh sentry.edge.config.ts.
│
◆  Added Sentry configuration to next.config.js. (you probably want to clean this up a bit!)
│
◆  Created pages/sentry-example-page.js.
│
◆  Created pages/api/sentry-example-api.js.
│
◆  Created .sentryclirc with auth token.
│
◆  Added .sentryclirc to .gitignore.

AbhiPrasad · 2023-05-16T14:07:24Z

Ah what also might be a thing is that we need to detect if an src directory is being used and put our example project in there instead of using top level pages.

alikleit · 2023-05-16T14:11:52Z

Hey @AbhiPrasad!

I'm running on windows, there's no git on the test project which I composed to make sure it's not a third party package on the actual project that is causing that issue.

Same error with manual setup..

However, this is the log from the wizard:

o  Login complete.
|
o  Select your Sentry project.
|
o  Installed @sentry/nextjs with npm.
|
*  Created fresh sentry.server.config.ts.
|
*  Created fresh sentry.client.config.ts.
|
*  Created fresh sentry.edge.config.ts.
|
*  Added Sentry configuration to next.config.js. (you probably want to clean this up a bit!)
|
*  Created pages\sentry-example-page.js.
|
*  Created pages\api\sentry-example-api.js.
|
*  Created .sentryclirc with auth token.
|
*  Added .sentryclirc to .gitignore.

joaomlap · 2023-05-16T15:12:39Z

Just want to say I have the exactly the same error which I had raised in StackOverflow:
https://stackoverflow.com/questions/76237075/sentry-next-js-13-4-webpack-supports-data-and-file-uris-by-default-you

lforst · 2023-05-16T15:16:46Z

Hm, I think a somewhat recent change introduced this bug. Lemme check.

timfish · 2023-05-16T15:35:17Z

Confirmed this on Windows. I'll check the potential fix!

lforst · 2023-05-16T15:37:05Z

Thanks @timfish!

timfish · 2023-05-16T15:49:25Z

That PR doesn't appear to fix it.

Here is the full error. I guess the paths aren't displayed correctly in this error because the back slash is an escape character!

> next-sentry-app@0.1.0 build
> next build

(node:22328) ExperimentalWarning: stream/web is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Failed to compile.

C:Users imDocumentsRepositoriesext-sentry-appsentry.server.config.ts
Module build failed: UnhandledSchemeError: Reading from "C:Users        imDocumentsRepositoriesext-sentry-appsentry.server.config.ts" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "c:" URIs.
    at C:\Users\tim\Documents\Repositories\next-sentry-app\node_modules\next\dist\compiled\webpack\bundle5.js:28:395974
    at Hook.eval [as callAsync] (eval at create (C:\Users\tim\Documents\Repositories\next-sentry-app\node_modules\next\dist\compiled\webpack\bundle5.js:13:28771), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (C:\Users\tim\Documents\Repositories\next-sentry-app\node_modules\next\dist\compiled\webpack\bundle5.js:13:25925)
    at Object.processResource (C:\Users\tim\Documents\Repositories\next-sentry-app\node_modules\next\dist\compiled\webpack\bundle5.js:28:395899)
    at processResource (C:\Users\tim\Documents\Repositories\next-sentry-app\node_modules\next\dist\compiled\loader-runner\LoaderRunner.js:1:5308)
    at iteratePitchingLoaders (C:\Users\tim\Documents\Repositories\next-sentry-app\node_modules\next\dist\compiled\loader-runner\LoaderRunner.js:1:4667)
    at runLoaders (C:\Users\tim\Documents\Repositories\next-sentry-app\node_modules\next\dist\compiled\loader-runner\LoaderRunner.js:1:8590)
    at NormalModule._doBuild (C:\Users\tim\Documents\Repositories\next-sentry-app\node_modules\next\dist\compiled\webpack\bundle5.js:28:395761)
    at NormalModule.build (C:\Users\tim\Documents\Repositories\next-sentry-app\node_modules\next\dist\compiled\webpack\bundle5.js:28:397789)
    at C:\Users\tim\Documents\Repositories\next-sentry-app\node_modules\next\dist\compiled\webpack\bundle5.js:28:81243

Import trace for requested module:
C:Users imDocumentsRepositoriesext-sentry-appsentry.server.config.ts
./src/app/page.tsx


> Build failed because of webpack errors

lforst · 2023-05-16T16:00:07Z

@timfish could you check out the latest commit and share the logs of the build before it crashes if you find the time? Thank you!

timfish · 2023-05-16T16:49:21Z

Here is the output:

TEST LOG {                                                                                                    
  sentryConfigFilePath: 'C:\\Users\\tim\\Documents\\Repositories\\next-sentry-app\\sentry.server.config.ts',  
  rp: 'C:\\Users\\tim\\Documents\\Repositories\\next-sentry-app\\src\\app\\layout.tsx',                       
  imp: '..\\..\\..\\sentry.server.config.ts'                                                                  
}                                                                                                             
TEST LOG {                                                                                                    
  sentryConfigFilePath: 'C:\\Users\\tim\\Documents\\Repositories\\next-sentry-app\\sentry.server.config.ts',  
  rp: 'C:\\Users\\tim\\Documents\\Repositories\\next-sentry-app\\src\\app\\page.tsx',                         
  imp: '..\\..\\..\\sentry.server.config.ts'                                                                  
}

After the error we see:

Import trace for requested module:
C:Users imDocumentsRepositoriesext-sentry-appsentry.server.config.ts
./src/app/page.tsx

./src/app/layout.tsx
Module not found: Can't resolve '......sentry.server.config.ts'

https://nextjs.org/docs/messages/module-not-found

./src/app/page.tsx
Module not found: Can't resolve '......sentry.server.config.ts'

https://nextjs.org/docs/messages/module-not-found

So it looks like there are two issues:

.replace(/\\/g, '/') so we only have url valid slashes
path.dirname(resourcePath) so the path is relative to the directory

Like:

templateCode = `import "${path.relative(path.dirname(this.resourcePath), sentryConfigFilePath).replace(/\\/g, '/')}";\n`.concat(templateCode);

timfish · 2023-05-16T16:51:22Z

Due to the incremental builds I spent forever trying to work out why I was not getting any console output after the first initial build!

I don't mind submitting a PR but wasn't sure if this was correct. Would you want to just exclude the import entirely if it isn't an absolute path?

    if (sentryConfigFilePath && path.isAbsolute(this.resourcePath)) {

rortan134 · 2023-08-22T23:10:52Z

Still getting this error on Next 13.4.19 Windows 10

Build failed: UnhandledSchemeError: Reading from "C:UsersDocumentsprojectnode_modules@sentryextjscjsconfig        emplatesequestAsyncStorageShim.js" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "c:" URIs.

lforst · 2023-08-23T10:30:43Z

@rortan134 what SDK version are you on?

rortan134 · 2023-08-23T10:49:50Z

@rortan134 what SDK version are you on?

I am on ^7.64.0

lforst · 2023-08-28T09:11:29Z

@rortan134 opened a PR to fix: #8875

rortan134 · 2023-09-05T09:10:57Z

@rortan134 opened a PR to fix: #8875

Hey @lforst, I just tested the release (7.66.0) and now it seems to load but I'm getting the following warning on console:

warn - The Sentry SDK could not access the RequestAsyncStorage module. Certain features may not work. There is nothing you can do to fix this yourself, but future SDK updates may resolve this.

lforst · 2023-09-05T09:14:00Z

@rortan134 Do you have some kind of unconventional node_modules structure? Can you try purging your dependencies and reinstalling them?

rortan134 · 2023-09-05T09:32:37Z

@rortan134 Do you have some kind of unconventional node_modules structure? Can you try purging your dependencies and reinstalling them?

I'm using npm workspaces, is it not compatible? Just did a fresh install and same thing 😪

lforst · 2023-09-05T09:34:40Z

@rortan134 I don't know what might cause this. Can you share a small reproduction example we could use to debug this further? Thanks!

rortan134 · 2023-09-11T19:01:58Z

Seems like #8977 found the reason

getsantry bot added the Status: Unrouted label May 16, 2023

getsantry bot added the Status: Untriaged label May 16, 2023

AbhiPrasad transferred this issue from getsentry/sentry May 16, 2023

AbhiPrasad added Status: Needs Information Package: nextjs Issues related to the Sentry Nextjs SDK and removed Status: Untriaged labels May 16, 2023

github-actions bot added the Waiting for: Team label May 16, 2023

AbhiPrasad assigned timfish May 16, 2023

lforst self-assigned this May 16, 2023

github-actions bot removed the Waiting for: Team label May 16, 2023

lforst mentioned this issue May 16, 2023

fix(nextjs): Inject init code via relative path #8135

Closed

timfish added Status: Confirmed and removed Status: Needs Information labels May 16, 2023

timfish mentioned this issue May 16, 2023

fix(nextjs): Import path issue on Windows #8142

Merged

lforst closed this as completed in #8142 May 17, 2023

lforst mentioned this issue Aug 28, 2023

fix(nextjs): Fix requestAsyncStorageShim path resolution on windows #8875

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Next 13 Module build failed UnhandledSchemeError #8133

Next 13 Module build failed UnhandledSchemeError #8133

alikleit commented May 16, 2023 •

edited

Loading

getsantry bot commented May 16, 2023

AbhiPrasad commented May 16, 2023

AbhiPrasad commented May 16, 2023

alikleit commented May 16, 2023 •

edited

Loading

joaomlap commented May 16, 2023 •

edited

Loading

lforst commented May 16, 2023

timfish commented May 16, 2023

lforst commented May 16, 2023

timfish commented May 16, 2023

lforst commented May 16, 2023

timfish commented May 16, 2023 •

edited

Loading

timfish commented May 16, 2023 •

edited

Loading

rortan134 commented Aug 22, 2023 •

edited

Loading

lforst commented Aug 23, 2023

rortan134 commented Aug 23, 2023

lforst commented Aug 28, 2023

rortan134 commented Sep 5, 2023 •

edited

Loading

lforst commented Sep 5, 2023 •

edited

Loading

rortan134 commented Sep 5, 2023

lforst commented Sep 5, 2023

rortan134 commented Sep 11, 2023

Next 13 Module build failed UnhandledSchemeError #8133

Next 13 Module build failed UnhandledSchemeError #8133

Comments

alikleit commented May 16, 2023 • edited Loading

Environment

Steps to Reproduce

Expected Result

Actual Result

Product Area

Link

DSN

Version

getsantry bot commented May 16, 2023

AbhiPrasad commented May 16, 2023

AbhiPrasad commented May 16, 2023

alikleit commented May 16, 2023 • edited Loading

joaomlap commented May 16, 2023 • edited Loading

lforst commented May 16, 2023

timfish commented May 16, 2023

lforst commented May 16, 2023

timfish commented May 16, 2023

lforst commented May 16, 2023

timfish commented May 16, 2023 • edited Loading

timfish commented May 16, 2023 • edited Loading

rortan134 commented Aug 22, 2023 • edited Loading

lforst commented Aug 23, 2023

rortan134 commented Aug 23, 2023

lforst commented Aug 28, 2023

rortan134 commented Sep 5, 2023 • edited Loading

lforst commented Sep 5, 2023 • edited Loading

rortan134 commented Sep 5, 2023

lforst commented Sep 5, 2023

rortan134 commented Sep 11, 2023

alikleit commented May 16, 2023 •

edited

Loading

alikleit commented May 16, 2023 •

edited

Loading

joaomlap commented May 16, 2023 •

edited

Loading

timfish commented May 16, 2023 •

edited

Loading

timfish commented May 16, 2023 •

edited

Loading

rortan134 commented Aug 22, 2023 •

edited

Loading

rortan134 commented Sep 5, 2023 •

edited

Loading

lforst commented Sep 5, 2023 •

edited

Loading