You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any way to setup npm so it doesn't load those folders on production, maybe via tampering with package.json? Currently folders such as
browser-version/test
test
benchmarks
test_lac
occupy up to 66%(800 MB) of package size, although they're definetely not needed in production. I know it sounds not too much, but in my case it's important. And wasn't this repo intended to be as little and dep-free as possible after all?
Btw if someone is wondering, I'm pretty sure maintainer is physically alive at least.
The text was updated successfully, but these errors were encountered:
Is there any way to setup npm so it doesn't load those folders on production, maybe via tampering with package.json? Currently folders such as
occupy up to 66%(800 MB) of package size, although they're definetely not needed in production. I know it sounds not too much, but in my case it's important. And wasn't this repo intended to be as little and dep-free as possible after all?
Btw if someone is wondering, I'm pretty sure maintainer is physically alive at least.
The text was updated successfully, but these errors were encountered: