We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@parcel/rust is installing binaries for all supported platforms, on every platform. This bloats the install footbrint by 165-169MB.
@parcel/rust
For example, with a fresh install (new, empty directory):
parcel should only install the one binary needed for the current host os/cpu architecture.
parcel
os
cpu
I know this is a non-trivial problem, but other projects seem to have solved this. E.g. esbuild ships it's binaries as separate optionalDependencies and relies on the package manager to decide which one to install. (It's worth noting that they had considerable discussion on this topic before settling on this solution.)
esbuild
optionalDependencies
The text was updated successfully, but these errors were encountered:
Yes, we definitely want this. It's just that somebody need to implement it.
https://github.com/parcel-bundler/lightningcss has this approach as well, and that seems to work well.
Previous discussion: #6483
Sorry, something went wrong.
and that seems to work well
...mostly. There are some issues with package managers not installing any of the optional dependencies sometimes.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs.
No branches or pull requests
Problem
@parcel/rust
is installing binaries for all supported platforms, on every platform. This bloats the install footbrint by 165-169MB.Current Behavior
For example, with a fresh install (new, empty directory):
Desired Behavior
parcel
should only install the one binary needed for the current hostos
/cpu
architecture.I know this is a non-trivial problem, but other projects seem to have solved this. E.g.
esbuild
ships it's binaries as separateoptionalDependencies
and relies on the package manager to decide which one to install. (It's worth noting that they had considerable discussion on this topic before settling on this solution.)The text was updated successfully, but these errors were encountered: