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
False Requirement: isolatedModules is set to true for babel when not using babel #31149
Labels
bug
Issue was opened via the bug report template.
Comments
10 tasks
timneutkens
added a commit
to timneutkens/next.js
that referenced
this issue
Nov 8, 2021
This is still required with SWC. The message just wasn't updated. Fixes vercel#31149
This requirement is still the same, we just didn't update the reason message, opened #31150 to update that. |
kodiakhq bot
pushed a commit
to timneutkens/next.js
that referenced
this issue
Nov 8, 2021
…#31150) This is still required with SWC. The message just wasn't updated. Fixes vercel#31149 ## 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 `yarn lint`
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. |
natew
pushed a commit
to natew/next.js
that referenced
this issue
Feb 16, 2022
…#31150) This is still required with SWC. The message just wasn't updated. Fixes vercel#31149 ## 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 `yarn lint`
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What version of Next.js are you using?
12.0.3
What version of Node.js are you using?
16.9.4
What browser are you using?
Chrome
What operating system are you using?
Ubuntu
How are you deploying your application?
vercel
Describe the Bug
A dependency does not have isolatedModules and thus breaks
next build
. We are not using babel anymore in favor of swc.The following mandatory changes were made to your tsconfig.json:
- isolatedModules was set to true (requirement for babel)
Then the build fails because of no isolated modules
Expected Behavior
Allow isolatedModules or enhance error message
To Reproduce
Set
isolatedModules
intsconfig.json
totrue
and runnext build
.The text was updated successfully, but these errors were encountered: