Hi there, I deployed the app on fly.io and it was successful, but when trying to connect it to github actions to make it an automatic deployment i get this error.
It’s a little weird to me that a build steps runs npm install node-sass
instead of having that defined in packages.json
(and/or the packages lock file). This part smells a little like it might be part of the issue.
(Altho perhaps that’s done to get around node-sass’s sensitivity to what version of Node is being run when it’s used.)
This error, however, I believe means that script file “scripts/install.js” isn’t executable by the user running sh -c node scripts/install.js
, or file scripts/install.js
is missing. It’s also possible that install.js
is doing something it doesn’t have permission to do.
I don’t really have a great idea on why that’s different in a github action! In theory, since it’s using a remote builder, it should be the same result you’d see no matter where you deployed from.
Thank you for your answer!
for the npm install node-sass
i just added it trying to solve the issue, it’s defined in the packages.json
for the versions, i don’t think it’s causing the issue, they are compatible as you can see:
Perhaps npm i --unsafe-perm node-sass
will work - which I got from googling that error, which led here: node-sass/vendor/linux-x64-64 : { Error: EACCES: permission denied · Issue #2824 · sass/node-sass · GitHub
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.