This will allow downstream consumers to require() the toolkit from GitHub and get an up-to-date bundle w/o it being including in the repository.
However, in order to build assets, devDependencies need to be installed, so the first step is probably to recursively call npm install to make them available. (The other alternative is to turn them into dependencies, but that substantially increases the footprint when npm-style module resolution is used.)
Ah, good idea. Will a single npm install (this will be subsequent to the initial npm install run when building the project initially) always work to pull in peerDependencies?
This will allow downstream consumers to
require()
the toolkit from GitHub and get an up-to-date bundle w/o it being including in the repository.However, in order to build assets,
devDependencies
need to be installed, so the first step is probably to recursively callnpm install
to make them available. (The other alternative is to turn them intodependencies
, but that substantially increases the footprint when npm-style module resolution is used.)