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

next build fails with The "path" argument must be of type string with WebWorker within workspaces #34064

Closed
andreypopp opened this issue Feb 7, 2022 · 4 comments · Fixed by #34087
Labels
Webpack Related to Webpack with Next.js.

Comments

@andreypopp
Copy link

Run next info (available from version 12.0.8 and up)

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Debian 5.15.5-2~bpo11+1 (2022-01-02)
Binaries:
  Node: 16.13.2
  npm: 8.1.2
  Yarn: 1.22.17
  pnpm: 6.30.0
Relevant packages:
  next: 12.0.10
  react: 17.0.2
  react-dom: 17.0.2

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:

webpack/runtime/compat
The "path" argument must be of type string. Received undefined

Expected Behavior

next build is expected to build this correctly

To Reproduce

This is using pnpm and workspaces. Note that I was able to reproduce this with yarn workspaces as well but in some configurations. Here I can reliably reproduce it with pnpm.

git clone git@github.com:andreypopp/next-repro-25484.git
cd ./next-repro-25484
pnpm install
(cd with-web-worker/ && pnpm run build)
@andreypopp andreypopp added the bug Issue was opened via the bug report template. label Feb 7, 2022
@balazsorban44
Copy link
Member

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.

@andreypopp
Copy link
Author

@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)

@balazsorban44
Copy link
Member

We identified the issue and this is being addressed, thanks!

@balazsorban44 balazsorban44 added Webpack Related to Webpack with Next.js. kind: bug and removed bug Issue was opened via the bug report template. labels Feb 8, 2022
@kodiakhq kodiakhq bot closed this as completed in #34087 Feb 8, 2022
kodiakhq bot pushed a commit that referenced this issue Feb 8, 2022
fixes #25484
fixes #34064

## Bug

- [x] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have helpful link attached, see `contributing.md`
natew pushed a commit to natew/next.js that referenced this issue Feb 16, 2022
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`
@github-actions
Copy link
Contributor

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Webpack Related to Webpack with Next.js.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants