Enhancement: verify current+vendored platform match during npm rebuild
See original GitHub issueThe pre-compiled dependencies placed in node_modules/sharp/vendor are platform-specific. Some people, including those using Meteor, use npm rebuild for cross-platform support so sharp should verify the current platform matches the vendored platform.
Whilst we could place the vendor directory under build and get the deletion of this via npm rebuild for “free”, this would involve re-downloading ~7MB of files that are already present.
Instead using platform-specific directories below vendor would make more sense, e.g. node_modules/sharp/vendor/darwin, node_modules/sharp/vendor/linux and node_modules/sharp/vendor/win32.
See also #637
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:7 (4 by maintainers)
Top Results From Across the Web
npm-rebuild
This command runs the npm build command on the matched folders. This is useful when you install a new version of node, and...
Read more >Node Sass couldn't find a binding for your current environment
First step would be to delete your node_modules and run npm install rather than rebuilding your node-sass. – Nikhil Nanjappa. Feb 28, 2019...
Read more >Npm install command failing with message "could not find ...
When I run the npm install command, npm starts downloading the dependencies. But then, suddenly, it stops with the error:
Read more >Manage npm packages - Visual Studio (Windows)
Starting in Visual Studio 2022 Preview 4, the npm package manager is available for CLI-based projects, so you can now download npm modules ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Please can you open a new issue for this. I’ll be able to take a look in a couple of weeks.
@lovell I faced similar problem like @mutaphysis mentioned.
on my dev machine (macOS) it works well. but on the production environment(AWS linux), it is not working…
I am using meteor and this library ( both of them are latest version )
And I am using elastic beenstalk to delploy then
I got error like below at eb-activity.log
I also tried the
npm clean ...onnode_modules/sharpsit still doesn’t work