3 ms·
Well, why did you choose packages that change quickly and are poorly documented then? There are packages that, OTOH, have up to zero dependencies, and haven't c
by tannhaeuser 5y ago
Well, why did you choose packages that change quickly and are poorly documented then? There are packages that, OTOH, have up to zero dependencies, and haven't changed in years; if you consider those stale, I guess nobody can help you.
- snek_case 5y agoI chose the most basic and common packages I could find (terser and rollup), and the changing, no longer valid command-line options I was talking about were command-line options of the npm package manager.
- hasperdi 5y agoCould you explain which command line options, since AFAIK npm options haven’t changed in years, especially the basic ones, eg npm install.
- JoeBot3000 5y agoThe majority of packages in JS land change quickly and are poorly documented, unfortunately :( There certainly are stable packages, but sometimes to do what you need to do there is no other option.