maintenance-book
maintenance-book copied to clipboard
”SurviveJS — Maintenance” book
I don't have much (okay, close to zero) experience with them, but looks like it's a good alternative to Travis.
I don't fully understand how it works, but it was recommended several times. https://johno.com/changesets/
We have to find and convince a maintenance expert to write a foreword for the book.
* Tools like [Leasot](https://github.com/pgilad/leasot) or [imdone](https://imdone.io/) (not so sure about this one and what it does exactly :-). * Why not to use [no-warning-comments](https://eslint.org/docs/2.0.0/rules/no-warning-comments) ESLint rule
some thoughts(but it should be more): + it is recommended to enable 2fa. + `npm audit`
https://eslint.org/blog/2019/01/future-typescript-eslint
https://twitter.com/wiekatz/status/1076112047866298368
Two at least: * Legacy vs. modern - If you do only a modern build, you can forget about standalone dist bundles and UMD (a big win) * Maintainer vs....
* I think you should add one line to talk about the runner ups and deprecated alternatives to npm in the intro about packages. Component and Bower comes to mind....