Open legobeat opened 1 year ago
Yes, this should be fixed.
Build locally (node-gyp approach) as lifecycle script?
We should do the same as swc/lightningcss/esbuild: one npm package per platform as optionalDependencies
: https://unpkg.com/browse/lightningcss@1.20.0/package.json
Not stale
yeah, this is huge file, which is causing problems when doing npm i from our self hosted artifactory, please resolve this, open to contribute if someone can mentor.
~/workspace $ du -h package 44K package/lib 36K package/src 137M package ~/workspace $ du -h trans.tgz 44M trans.tgz
bump
🐛 bug report
As of
@parcel/transformer-js@2.0.0-nightly.657
(ba57b6501632703d68923b214b0c0f6d47a34b1f), the published npm package contains prebuilt swc binaries for 8 platforms. In the latest version of the package, these add up to 150 MiB.I tried searching for mentions of this being a conscious decision but coming up short, this issue asks if there are changes that can be done in bundling to bring the installation size of this package down.
🤔 Expected Behavior
I can use have a bunch of isolated gatsby environments checked out side-by-side an a consumer-grade laptop.
😯 Current Behavior
The
node_modules
directories fill up the disk quickly.💁 Possible Solution
Build locally (node-gyp approach) as lifecycle script?