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
Unable to run next on canary branch: Cannot find module './polyfills/polyfill-nomodule' #40334
Closed
1 task done
Labels
Developer Experience
Issues related to Next.js logs, Error overlay, etc.
Comments
github-actions
bot
added
the
please verify canary
The issue should be verified against next@canary. It will be closed after 30 days of inactivity
label
Sep 7, 2022
balazsorban44
removed
the
please verify canary
The issue should be verified against next@canary. It will be closed after 30 days of inactivity
label
Sep 7, 2022
balazsorban44
added
Developer Experience
Issues related to Next.js logs, Error overlay, etc.
and removed
bug
Issue was opened via the bug report template.
labels
Sep 8, 2022
11 tasks
Currently, you'll need an initial |
kodiakhq bot
pushed a commit
that referenced
this issue
Sep 30, 2022
Utilize `turbo` for `dev`, and make sure polyfills are built. Fixes #40334 Another option would be to document that an initial `pnpm build` is necessary in [`CONTRIBUTING.md`](https://github.com/vercel/next.js/blob/canary/contributing.md#developing). ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)
BowlingX
pushed a commit
to BowlingX/next.js
that referenced
this issue
Oct 5, 2022
Utilize `turbo` for `dev`, and make sure polyfills are built. Fixes vercel#40334 Another option would be to document that an initial `pnpm build` is necessary in [`CONTRIBUTING.md`](https://github.com/vercel/next.js/blob/canary/contributing.md#developing). ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Verify canary release
Provide environment information
Tried on 3 different platforms: Linux x86_64, MacOS arm64, and MacOS x86_64. Tried also with different nodejs versions from 14 through 18.
A few example environments:
What browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
Describe the Bug
Running any example or test fails, cannot find polyfill-nomodule.
Expected Behavior
Should be able to run without that error!
Link to reproduction
https://github.com/vercel/next.js
To Reproduce
The text was updated successfully, but these errors were encountered: