@pmoscode/node-package-builder v1.1.75

The Node Package Builder

This simple helper gets handy if you have to manage multiple package.json versions in one Node project.

So, why would you need that? For example if you have an application, module or ... and you need to run it on different architectures, like amd64, armV6, armV7, ... or you have multiple targets (native, cloud foundry, ...)

With NPB you can easily manage these challenges.

You need NodeJS version > 14.15 or 16.10 or 18.0 or 20.0

Installation

Local installation:

npm install @pmoscode/node-package-builder

or

yarn add @pmoscode/node-package-builder --dev

Global installation:

npm install -g @pmoscode/node-package-builder

or

yarn global add @pmoscode/node-package-builder

Example

package.json

Let's take this as an example:

{
  "name": "my-app",
  "scripts": {
    "start": "node app.js",
    "test": "jest"
  },
  "version": "0.0.1",
  "engines": {
    "node": "0.8.x"
  },
  "license": "MIT"
}

cf.json

Here an example for an imaginary cloud foundry change (place it in "envs" folder by default):

{
  "name": "cf-app",
  "subdomain": "myapp-cf",
  "scripts": {
    "start": "node app.js --some-parameters"
  },
  "dependencies": {
    "something-cf-specific": "1.0.3"
  }
}

After run (from the root of your project)

npb cf

you will get a modified package.json:

{
  "name": "cf-app",
  "scripts": {
    "start": "node app.js --some-parameters",
    "test": "jest"
  },
  "version": "0.0.1",
  "engines": {
    "node": "0.8.x"
  },
  "license": "MIT",
  "dependencies": {
    "something-cf-specific": "1.0.3"
  }
}

Restore original

When you run npb, it will create a backup of the original package.json. To restore this one, just run

npb

CLI parameters

Code documentation

Here you can find the Code documentation: https://pmoscode.github.io/node-package-builder/