loadtest URL [-n requests] [-c concurrency] [-k] [--rps requests_per_second]
npm install @mk.kakarla/node-clusteringloadtest URL [-n requests] [-c concurrency] [-k] [--rps requests_per_second]
loadtest http://localhost:1288/api/5000000 -n 1000 -c 100
Set the max number of requests with -n,
and the desired level of concurrency with the -c parameter.
Use keep-alive connections with -k whenever it makes sense, which should be always except when you are testing opening and closing connections
https://www.npmjs.com/package/loadtest
To publish to a scope, you can either:
Change the name to @username/package-name manually in package.json
Run npm init --scope=username instead of npm init
If your repository has a scope, you need to adjust the publish command slightly:
npm publish --access public
This means publishing a package involves many steps. At the very least, you need to:
Run tests (if there are any)
Update version in package.json according to Semver
Create a git tag according to Semver
Push the package to Github
Push the package to npm
Create release notes for every update