đŚ Allows you to publish your npmjs bundled packages without dependencies.
MIT License
No Dependencies package allows you to publish your npm bundled packages without dependencies.
If you build your project (e.g. you're using Webpack) and trying to load your package to npmjs, you will found that all dependencies install as well with the package. To prevent it, this package exists.
Just install the package to your repo:
$ npm i no-dependencies
Or install it globally and use in any repo:
$ npm i no-dependencies -g
After all, just call the package:
$ no-dependencies
Or call with a specified command:
$ no-dependencies --exec "npm i"
Or call or parts separetely:
$ no-dependencies --before && npm i && no-dependencies --after
$ no-dependencies
â Standard scenario
âď¸ Read the ./package.json
âď¸ Created a ./package.bak.json
âď¸ Deleted dependencies from the ./package.json
âď¸ Write a new ./package.json without dependencies
// ... npm publish result
âď¸ Executed the command: npm publish
âď¸ Deleted the ./package.json
âď¸ Copy ./package.bak.json to ./package.json
âď¸ Deleted the ./package.bak.json
âď¸ Deleted all temp files!
âď¸ Done!
List all commands and options:
$ no-dependencies --help
Usage: no-dependencies [options]
Allows you to publish packages without dependencies. Usefull when you publish a built bundle and don't want to install dependencies
Options:
-V, --version output the version number
-b, --before creates a package.json backup and deletes dependencies
-e, --exec <command> executes a specified command with a clean package.json. Default is: type "./package.json"
-a, --after returns back a backuped package.json
-d, --debug leaves backup and result files
-c, --clear cleares all temp files. Uses with or after the "--debug" command
-h, --help display help for command
If you publish a package without dependencies, they won't install.
So it just creates a copy of your package.json, deletes all dependencies, the call specified command and returns back the old package.json
Created with ⤠by Dmytro Vakulenko, 2020.