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

[12.0.2-canary.7] broken swc dependencies #30583

Closed
ezracelli opened this issue Oct 28, 2021 · 3 comments · Fixed by #30589
Closed

[12.0.2-canary.7] broken swc dependencies #30583

ezracelli opened this issue Oct 28, 2021 · 3 comments · Fixed by #30589
Labels
bug Issue was opened via the bug report template.

Comments

@ezracelli
Copy link

ezracelli commented Oct 28, 2021

What version of Next.js are you using?

12.0.2-canary.7

What version of Node.js are you using?

16.12.0

What browser are you using?

N/A

What operating system are you using?

macOS

How are you deploying your application?

N/A

Describe the Bug

optionalDependencies includes @next/swc-.gitignore and @next/swc-.linux-x64-musl, which aren't real packages and so break yarn install.

logs:

➤ YN0000: ┌ Resolution step
➤ YN0035: │ @next/swc-.gitignore@npm:12.0.1: The remote server failed to provide the requested resource
➤ YN0035: │   Response Code: 404 (Not Found)
➤ YN0035: │   Request Method: GET
➤ YN0035: │   Request URL: https://registry.yarnpkg.com/@next%2fswc-.gitignore
➤ YN0000: └ Completed in 3s 646ms
➤ YN0000: Failed with errors in 3s 652ms

package.jsons pulled from unpkg.com:

12.0.2-canary.6:

image

12.0.2-canary.7:

image

Expected Behavior

yarn install should succeed.

To Reproduce

yarn add [email protected]

@ezracelli ezracelli added the bug Issue was opened via the bug report template. label Oct 28, 2021
@ijjk
Copy link
Member

ijjk commented Oct 29, 2021

Hi, thanks for reporting this, it should be fixed in v12.0.2-canary.8, please update and give it a try!

@ezracelli
Copy link
Author

yep looks great! thanks for the quick fix @ijjk 😁

@balazsorban44
Copy link
Member

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.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants