51–60 of 66 posts
Earlier quoted context omitted.
Man it's free code, you're reading into this far too much.
I'm trying really hard to see what price has to do with anything I've said.
This line particularly reveals your very sad flavor of entitlement:
> hey i did this at 2am out of frustration, i chose the tools that i knew best, use it at your own risk, opensourced to share knowledge and to access it from my own projects, not as a "productified" software.
Earlier quoted context omitted.
Many authors are strangely against it for some reason. One time I sorted my node_modules by size and opened issues for the top offenders, you can see their resistance here: https://github.com/crypto-browserify/sha.js/issues/5 https://github.com/medikoo/es5-ext/issues/11
Speaking as very-much-not-a-JS-developer: Isn't this essentially the same problem Linux package managers solve with -dev, -doc, and -dbg packages? I.e. the default install only contains the minimum necessary to use a program, and if you need the header files/documentation/debug symbols, you can just install them separately. Is it too hard to meaningfully separate these parts of a package, or is it more of a philosoph…
*
!dist/**/*Shouldn't this be handled entirely by npm? If these files are unnecessary why do they get downloaded in the first place?
Shouldn't this be handled entirely by npm? If these files are unnecessary why do they get downloaded in the first place?