node-prune

It's especially good for deployments to AWS Lambda.

Awesome idea. Especially if you’re packaging your projects via something like Docker this can shave hundreds of megabytes. (Even if you’re using the Docker layer cache, any…

Love it. Saved 600MB... and test cases still passed :) I ported it to bash really quick, as thats probably easier for people to drop into their dotfiles if they don't have a…

It looks like it removes the files necessary for "npm install" assuming that the module will do npm install immediately when you install it. This is not true for all cases…

Awesome idea. Especially if you’re packaging your projects via something like Docker this can shave hundreds of megabytes. (Even if you’re using the Docker layer cache, any…

No it should NOT be handled by npm. Imagine some npm project really needs those files. Like module that is rendering markdown files to html. If npm would be that "smart" to strip…

Shouldn't this be handled entirely by npm? If these files are unnecessary why do they get downloaded in the first place?

Ideally people use the "files" array. It might be nice if someone writes a bot to go around and fix large packages by adding that.

I guess there is the "files" and ".npmignore" which handle these, but they don't seem to be widely used in the community.

https://github.com/tj/node-prune/blob/master/prune.go#L57 Doesn't this also result in .d.ts files being removed? These are type declaration files (Kinda like C's .h files) that…

ts-node no longer works.

Is this serious? I mean, kudos for helping push node module developers to make better use of `.npmignore` et al, but this project strikes me as overly snarky or even trolling...…

Even better: submit a PR auto fix these issues on the corresponding GitHub repo when pruning

Rather than two giant 440px high images consisting of tiny text in the readme I'd quite love to read exactly what it does and why. Does it prune files in modules that are not…

Maybe documentation should include uses cases? Newer users to npm + node might think this does something different. Just a suggestions.

No disrespect to TJ (he did many awesome projects I use almost daily), but wouldn't simple: 'find node_modules -not -regex ".*.[js,json]" -delete' do the same job? Why project in…

Usually I don't care about what language an executable is written in. After all, as a user I'm just interested in whether it executes or not. But these small-software situations…

Shouldn't this be handled entirely by npm? If these files are unnecessary why do they get downloaded in the first place?

This is completely useless because npm still downloads those files and the hdd space is pretty negligeble. It should def go under the category of troll driven development. This…

The Yarn autoclean command also does something like this: https://yarnpkg.com/lang/en/docs/cli/autoclean/

you're looking for `yarn autoclean`. they have `.yarncleanrc` IIRC

No disrespect to TJ (he did many awesome projects I use almost daily), but wouldn't simple: 'find node_modules -not -regex ".*.[js,json]" -delete' do the same job? Why project in…

Ideally people use the "files" array. It might be nice if someone writes a bot to go around and fix large packages by adding that.

We've started publishing modules with a whitelist in the npmignore to help combat this. ``` * !dist/**/* ```

I've been thinking about this in a different way: what about bundling things with rollup.js? Then each package in require() would be just a package.json and an index.js. I think…

Wouldnt it make more sense to bundle, minify and treeshake your package than to delete unused files in node_modules? Tree shaking will remove unsused code even from files you are…