I’m pushing my changes to the repository on github to test if the auto deployment works and it did, but the build keep failing with the same error.
bindings not accessible from watchpack-chokidar2:fsevents
The error occurred when it run npm ci. I try to run npm ci and build my app locally and nothing wrong happen. I also try the force rebuild and deploy action but still the same error.
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
I fix this issue by specifying node
and npm
version inside package.json
to version 16
and 7
. The reason why that specific version is because many of fsevents
issue is fixed in npm version 7
and App Platform (if I’m not mistaken) by default using node version 12
and npm version 6
.
This comment has been deleted
Click below to sign up and get $100 of credit to try our products over 60 days!
Hi @nicolecusi
I’ve posted an answer for this issue. Hopefully it can help your case.
Originally had this under answers, moved to comments.
Hi @rakakhairil,
Did you manage to find a solution? I’m running into the same error. It’s odd because I have another app that’s running fine in the new App Platform and it contains the fsevents dependency in the package.json file.
Hi @sergioturpin,
Thank you for commenting. So what do you recommend as a solution? Because this error happen when app platform run npm ci so I guess modify the build command did nothing? Do I need to list
fsevents
as dependency in mypackage.json
?Sorry for the follow up question this is my first time deploying anything on cloud.
Hi @rakakhairil,
I think it’s not a mistake, it’s a warning. When you work in macOS environment the package provides native access to fsevents and because of you run the production application in another environment fsevents is omitted as irrelevant.
Best regards, Sergio Turpín