-
Notifications
You must be signed in to change notification settings - Fork 399
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
newrelic module needs a lot of storage space #77
Comments
I was still on 1.0.0 locally. Upgrading to 1.0.1 results in 57mb |
This is due to an npm bug related to how it deals with the combination of bundledDependencies and multiple node_modules folders in a repo. That module should be around 300KiB as a tarball, but I forgot a step in the build process. I'll republish 1.0.1 in a more svelte form later today. |
Great, thanks! |
Republished a bazillion times smaller. Sorry about that! |
Confirmed. Dropped from 59M to 2.6M |
…4d889c9d6de9abfff [Snyk] Security upgrade newrelic from 9.5.0 to 10.3.1
changing gh token to the org level value
Updated readme with community-plus header
Updated readme with community-plus header
…moment-2.29.4 Bump moment from 2.29.2 to 2.29.4
I've noticed that my slug size on Heroku (https://devcenter.heroku.com/articles/slug-compiler) increased from about 30megs to over 70megs just because I added the newrelic module.
Running
du | sort -g
on the dyno these are the bottom linesI don't think the
/test
folder should be part of the release on npm. I suggest adding a.npmignore
file.Funny enough, on my dev machine the
test
folder only weighs about 1meg, whereas it's 57meg on Heroku.The text was updated successfully, but these errors were encountered: