Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reading from "node:fs" is not handled by plugins (Unhandled scheme). #32935

Closed
heart-er opened this issue Jan 1, 2022 · 3 comments
Closed

Reading from "node:fs" is not handled by plugins (Unhandled scheme). #32935

heart-er opened this issue Jan 1, 2022 · 3 comments
Labels
bug Issue was opened via the bug report template. please add a complete reproduction The issue lacks information for further investigation

Comments

@heart-er
Copy link

heart-er commented Jan 1, 2022

What version of Next.js are you using?

12.0.7

What version of Node.js are you using?

16.10.0

What browser are you using?

chrome

What operating system are you using?

macOS

How are you deploying your application?

Other platform

Describe the Bug

when i use node-fetch http request in getServerSideProps, next throws error.

This is error information:
[1] Module build failed: UnhandledSchemeError: Reading from "node:fs" is not handled by plugins (Unhandled scheme).
[1] Webpack supports "data:" and "file:" URIs by default.
[1] You may need an additional plugin to handle "node:" URIs.
[1] Could not find files for /post/[id] in .next/build-manifest.json

Expected Behavior

Expect no error.

To Reproduce

none

@heart-er heart-er added the bug Issue was opened via the bug report template. label Jan 1, 2022
@timneutkens timneutkens added the please add a complete reproduction The issue lacks information for further investigation label Jan 1, 2022
@timneutkens
Copy link
Member

fetch is supported by default. You don't have to install or add node-fetch anywhere.

@balazsorban44
Copy link
Member

I believe this might be a duplicate of #28774

@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Feb 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template. please add a complete reproduction The issue lacks information for further investigation
Projects
None yet
Development

No branches or pull requests

3 participants