-
Notifications
You must be signed in to change notification settings - Fork 118
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
Does not work with Node v4.2.3 #108
Comments
That looks like an issue with elastic beanstalk, not node or fsevents. You need to fix the EACCES error somehow. |
Hi, that was also my thought but here is the response I got from AWS tech support:
|
I kind of doubt that's it (and I assume you mean |
I'm facing the same issues with AWS-- seems like a temporary solution can be found here. |
I had the same issue with the dependency coming from the nodemon module. After uninstalling nodemon it worked fine. See issue. Maybe you have the same issue with the forever-monitor. |
npm config set unsafe-perm true |
Posting in hopes to spare someone else the grief of debugging this error. The issue was fixed for me by adding a trailing slash to the node_modules folder in .ebignore .ebignore
Without the trailing slash, eb will upload your local node_modules folder - dev dependencies and all. |
Thanks a lot, @unreal0 ! Your solution helped me (contrary to others). I have made it easier to find via SO: https://stackoverflow.com/questions/46001516/beanstalk-node-js-deployment-node-gyp-fails-due-to-permission-denied/46001517#46001517 |
Add a file named .npmrc to the application with the content:
Now deploy your code. It should work. |
Hi guys I followed the steps to upload a Backend Express.js app with Beanstalk but I keep getting same error... What else could it be? I have the .npmrc file in my app with:
|
I think it depends on the version of npm. From the logs I can see that unsafe-perm works only <= 6 npm version. 2022-09-15T12:13:52.569+02:00 | npm ERR! sharp: - For npm <= v6, try again with the "--unsafe-perm" flag |
The text was updated successfully, but these errors were encountered: