there's a little tool for managing them
so you can subscribe to package publications and so on
thanks to semver it gets the new content
then it triggers netlify build (another hook)
so if i edit site content through github ui, it should go through these
you could do this for docs etc.
super nice way to manage
it fits well
@bebraw i've never used, nor heard, of
npm-ci. i think yarn is too far in the lead for a little bit of speed to make people care about another manager - i'd almost take yarn over npm installs simply because of the better illustrated install progress. but i prefer the quick-start of npm-init -y -> write-my-code
but i have used this a couple of times now: npm-check (checks for unused dependencies)
Component and Bower comes to mind.
Also another sentence about stuff like jspm, duojs, yarn and pnpm wouldn't hurt.
basically the book was in hold for most of the year due to other business (paid work) but i may be able to free some time in the Fall
just wanted to help you out
i have a long personal list of things to add/change too
i thought about changing the book so that you can see legacy/modern option
if you go with only modern, you don't have to worry about things like dist bundles anymore and the problem of packaging becomes much simpler
another dimension might be perspectives (maintainer, user, ???)
i see UMD as legacy
if we did the book right, it would help product people too
..