-
Notifications
You must be signed in to change notification settings - Fork 27.4k
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
next build
fails with The "path" argument must be of type string
with WebWorker within workspaces
#34064
Comments
Just curious, is this actually related to workspaces or have you been able to reproduce in a single application as well? We should try to keep the reproduction minimal if that's the case. |
@balazsorban44 this is the minimal repro I've been able to come up with, sorry. I think this is related to workspaces, yeah (both with yarn and pnpm, though with yarn it doesn't manifest itself in this repro) |
We identified the issue and this is being addressed, thanks! |
fixes vercel#25484 fixes vercel#34064 ## Bug - [x] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md`
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. |
Run
next info
(available from version 12.0.8 and up)What version of Next.js are you using?
12.0.10
What version of Node.js are you using?
16.13.2
What browser are you using?
Chrome, Safari, ...
What operating system are you using?
Linux
How are you deploying your application?
next build
Describe the Bug
With the setup described at https://github.com/andreypopp/next-repro-25484
next build
command fails with:Expected Behavior
next build
is expected to build this correctlyTo Reproduce
This is using
pnpm
and workspaces. Note that I was able to reproduce this withyarn
workspaces as well but in some configurations. Here I can reliably reproduce it withpnpm
.The text was updated successfully, but these errors were encountered: