Skip to content
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

Switch to prebuildify for installation #1812

Open
azerum opened this issue Dec 11, 2024 · 0 comments
Open

Switch to prebuildify for installation #1812

azerum opened this issue Dec 11, 2024 · 0 comments

Comments

@azerum
Copy link

azerum commented Dec 11, 2024

Summary

Suggestion

Use prebuildify instead of prebuild-install. Unlike prebuild-install, prebuildify ships all precompiled binaries with the package

This simplifies deployment by a lot, since now, no matter what architecture of machine where the package was installed, node_modules can be copied to machine with other architecture and code will still work

Supposedly this will also fix #1731, see this comment

prebuild-install README.md itself recommends to use prebuildify and lists some reasons

My use case

I use Rush.js for monorepo management. It has command rush deploy that creates a directory to deploy specific project from monorepo. It includes:

  • Files of project
  • Files of projects from monorepo it depends on
  • Installed NPM packages

The last point is the problem: if I run rush deploy on my macOS, it will generate directory with sqlite3 binary for macOS inside. Copy this directory on Linux server and it won't work

Proposed implementation

See docs of prebuildify

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant