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

Jump to bottom

Packaging of binaries #877

Open
anton-johansson opened this issue Jun 8, 2021 · 3 comments
Open

Packaging of binaries #877

anton-johansson opened this issue Jun 8, 2021 · 3 comments

Comments

@anton-johansson
Copy link

Hi! This is the first time I come accross a NodeJS package that uses external binaries. It wasn't a problem until today, when Github Releases started giving us 503 for a short period.

That got me thinking. Isn't there a better way of packaging binaries? We use a local NPM registry in between the official NPM registry and our developers, and we use it to cache packages. This is useful for performance but it also great if upstreams are down for whatever reason.

Isn't it possible to package the binary inside the NPM package somehow?
@recrsn
Copy link
Collaborator

recrsn commented Jun 11, 2021

The binaries are pre-complied and hosted as a convenience. Many other libs do it (sass, fsevents) and fall back to compiling themselves when it can't be downloaded.

Including binaries for all precompiled architectures is not currently possible (every binary needs a different architecture), but I am looking for ways to make them. Feel free to suggest any.

@anton-johansson
Copy link
Author

Would it be a valid strategy to publish one NPM package for each architechture?

@thom-nic
Copy link
Contributor

@anton-johansson you might be interested in #665

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@thom-nic @anton-johansson @recrsn