Skip to content

Instantly share code, notes, and snippets.

@bcoe
Created February 6, 2017 19:29
Show Gist options
  • Save bcoe/83b2b87360c6d2aa763838e749c5c863 to your computer and use it in GitHub Desktop.
Save bcoe/83b2b87360c6d2aa763838e749c5c863 to your computer and use it in GitHub Desktop.
lerna-bundle.txt
For yargs, I'm picturing a structure something like this:
yargs
lib
command.js
validation.js
packages:
yargs-parser
index.js
package.json
test/
argsert
index.js
package.json
test/
cliui
test/
index.js
yargs.js
package.json
I'd like to release a single yargs module, that includes the packages in the /packages folder as part of its tarball.
I'd also like to release each module individually:
https://www.npmjs.com/package/yargs-parser
https://www.npmjs.com/package/cliui
... etc.
The benefit of this would be, I cut down on the number of HTTP requests required to install yargs, it becomes one tarball with everything.
But, folks can still build on top of the individual components that are used by yargs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment