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

npm on CI fails with fsevents not accessible from jest-haste-map #23168

Closed
cfbender opened this issue Mar 17, 2021 · 4 comments
Closed

npm on CI fails with fsevents not accessible from jest-haste-map #23168

cfbender opened this issue Mar 17, 2021 · 4 comments
Labels
bug Issue was opened via the bug report template. please verify canary The issue should be verified against next@canary. It will be closed after 30 days of inactivity

Comments

@cfbender
Copy link

What version of Next.js are you using?

10.0.6

What version of Node.js are you using?

14.16.0

What browser are you using?

Chrome, Firefox

What operating system are you using?

Linux

How are you deploying your application?

next start

Describe the Bug

Running npm ci in a CI environment fails with the error:

npm ERR! fsevents not accessible from jest-haste-map

Expected Behavior

Install completes successfully

To Reproduce

Upgrade to 10.0.6 and install with npm ci on node:lts container

This could be related to #21343.

We need to use 10.0.7+ in order to utilize the fix applied in #22072

Thanks!

@cfbender cfbender added the bug Issue was opened via the bug report template. label Mar 17, 2021
@cfbender
Copy link
Author

As a workaround, I installed webpack@latest to devDependencies and put

future: {
  webpack5: true,
}

to the next config.

@jankaifer
Copy link
Contributor

This should be fixed if updating webpack helped you.
Could someone check if it still happens in next@canary?

@jankaifer jankaifer added the please verify canary The issue should be verified against next@canary. It will be closed after 30 days of inactivity label Nov 25, 2022
@balazsorban44
Copy link
Member

This issue has been automatically closed because it wasn't verified against next@canary. If you think it was closed by accident, please leave a comment. If you are running into a similar issue, please open a new issue with a reproduction. Thank you.

@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 Jan 26, 2023
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. please verify canary The issue should be verified against next@canary. It will be closed after 30 days of inactivity
Projects
None yet
Development

No branches or pull requests

3 participants