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
Windows: EPERM: operation not permitted, symlink #1969
Labels
Comments
The message |
lovell
changed the title
AWS Node.js 8.10 Deprecation
Windows: EPERM: operation not permitted, symlink
Nov 15, 2019
See also #1671 |
Yep, that works! |
In my case was the antivirus !! |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Repository owner
locked and limited conversation to collaborators
Dec 31, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi all.
On our project, we are using the AWS Lambda function written for Node.js 8.10 target platform.
And our Teamcity server is running on Windows AMI.
That is why we are using the post-install hook to change the windows bin of Sharp lib to the Linux one with such cmd:
Now I'm trying to migrate to the Node.js 10.x and the cmd:
npm install --arch=x64 --platform=linux --target=10.15.0 sharp
gives me something that I cant understood correctly:
As I understood, it tries to load the 'libvips' and build the bin on my local Windows PC using Python for Linux one?
Does it the correct way to install Sharp lib and how it would be on Teamcity.
Or there is another correct way to do this migration?
I do not know much about NodeJS and all this stuff.
Thanks!
The text was updated successfully, but these errors were encountered: