-
Notifications
You must be signed in to change notification settings - Fork 26.6k
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
The "path" argument must be of type string or an instance of Buffer or URL (react-dom
)
#31552
Comments
react-dom
)
FYI @sokra |
Same here. When I use Next.js v12.0.5-canary.0 or v12.0.5-canary.6,
Running I also tried |
Let’s hope that #31759 works as a fix 🤞 UPD: It did not 😅 |
To test with next.js >= v12.0.5-canary.10 after resolution of bug #31812. |
It still persists with |
Yep, upgrading to Next v12.0.5-canary.14 did not help me in kachkaev/njt#161. I tried setting UPD: Next 12.0.6 → no improvement |
"yarn add next@12.0.4" fixed it for me. Thank you! |
x-ref [#31552 ](#31552) x-ref #32115 x-ref #32546 x-ref #32721 Since this PR #31455 is merged, `enhanced-resolve` dependency's resolved field is changed which caused broken yarn pnp. I am not sure how this field has been changed or this is intentional or not When I install webpack locally, `enhanced-resolve`'s resolved field in lock file is always `registry.yarnpkg.com` not `codeload.github.com` ## Bug - [x] 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` Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com> Co-authored-by: JJ Kasper <22380829+ijjk@users.noreply.github.com>
Looks like this issue got fixed in |
I still get yarn errors if I update Next past 12.0.4. Any ideas? Everything seems to work great <= 12.0.4. Thanks!
|
@lenzi-erickson try Alternatively you can use 12.0.8, but set experimental -> swcFileReading = false in next.config.js |
What version of Next.js are you using?
12.0.5-canary.0-12.0.8-canary.20
What version of Node.js are you using?
14.17.0
What browser are you using?
Irrelevant
What operating system are you using?
Windows
How are you deploying your application?
Irrelevant
Describe the Bug
I updated
next.js
from v12.0.4 to v12.0.5-canary.0 and I got a compiling error fromreact-dom
.Expected Behavior
No error
To Reproduce
yarn init -y
yarn set version berry
yarn add next@canary react react-dom
pages
foldernext.config.js
file ( reason ):yarn next
The text was updated successfully, but these errors were encountered: