Enhances npm with additional configuration and tool management capabilities, including a key-value store for project setups.
Go to file
2019-09-16 13:19:42 +02:00
test BREAKING CHANGE(scope): change to @pushrocks scope 2018-08-31 01:11:09 +02:00
ts fix(core): update 2019-09-16 13:19:42 +02:00
.gitignore fix(core): update 2019-09-16 13:19:42 +02:00
.gitlab-ci.yml fix(core): update 2019-09-16 13:19:42 +02:00
.snyk BREAKING CHANGE(scope): change to @pushrocks scope 2018-08-31 01:11:09 +02:00
npmextra.json fix(core): update 2019-05-10 16:55:39 +02:00
package-lock.json 3.0.6 2019-09-16 13:18:45 +02:00
package.json fix(core): update 2019-09-16 13:19:42 +02:00
README.md fix(core): update 2019-09-16 13:19:42 +02:00
tslint.json fix(core): update 2019-05-10 16:55:39 +02:00

@pushrocks/npmextra

do more with npm

Status for master

build status coverage report npm downloads per month Known Vulnerabilities TypeScript node JavaScript Style Guide

Usage

Use TypeScript for best in class instellisense.

Using npmextra for managing toolconfigs

The main purpose of npmextra is to configure different tools using one npmextra.json. This way complex setups avoid additional complexity caused by too many configuration files.

npmextra.json

{
  "sometool": {
    "defaultKey1": "awesomeValueFromConfig"
  }
}
import { Npmextra } from 'npmextra';

let myNpmExtra = new Npmextra('my/path/to/cwd'); // cwd argument is optional
mergedData = myNpmExtra.dataFor('sometool', {
  // gets merged with whatever is in the configfile
  defaultKey1: 'defaultValue1', // so this will get overwritten with "awesomeValueFromConfig"
  defaultKey2: 'defaultValue2' // this one will pass through unaltered
});

Tools that already use the config feature of npmextra

Using the KeyValueStore

For further information read the linked docs at the top of this readme.

MIT licensed | © Lossless GmbH | By using this npm module you agree to our privacy policy

repo-footer