Removes and replaces configuration keys in 'package.json' before creating an NPM package.
npm install clean-packageThis clean-package tool is used for removing development configuration from 'package.json' before publishing the package to NPM.
``bash`
npm install clean-package --save-dev
The clean-package tool works directly on the 'package.json' file, to avoid breaking the NPM lifecycle. This allows you to add a script to the 'package.json' to clean the file during packing.
`json`
{
"name": "my-package",
"version": "1.0.0",
"scripts": {
"prepack": "clean-package",
"postpack": "clean-package restore"
}
}
When the "prepack" script executes, a backup of the original package.json will be created. Ensure this file doesn't make it into your release package.
One way to accomplish this is to add the following to your .npmignore file:
`ignore`
*.backup
See CLI Usage for independent usage instructions.
#### JSON Configuration Files
Options can be configured in clean-package.config.json at the root of your project (where the package.json is).
`json`
{
"indent": 2,
"remove": [
"eslintConfig",
"jest"
]
}
Alternatively, you can choose to specify your configuration from within package.json using the clean-package key like so:
`js
{
"name": "my-package",
"version": "1.0.0",
"clean-package": {
"indent": 2,
"remove": [
"eslintConfig",
"jest"
]
},
// Or, a file path to a configuration.
"clean-package": "./build/clean-package.config.js"
}
`
#### JavaScript Configuration File
You can also create the configuration using JavaScript in the clean-package.config.?(c|m)js at the root of your project:
`js`
module.exports = {
indent: '\t',
replace: {
'config.port': '8080'
}
};
String'./package.json.backup'package.json will be backed up.
String | Number2package.json. See the space parameter of JSON.stringify for more information.
String[] | (keys: String[]) => String[]Specifies the keys to be removed from the cleaned package.json; otherwise, null when nothing is to be removed.
Deeper keys can be accessed using a dot (e.g., 'key.keyInsideKey'). Likewise, arrays are accessible using brackets (e.g., 'key.arrKey[0]').
To remove keys that contain a dot, the dot must be escaped. For example, 'exports.\\.' will target "exports": { "." }
Object | (pairs: Object) => ObjectSpecifies the keys to be replaced in the cleaned package.json; otherwise, null when nothing is to be replaced.
Deeper keys and arrays are accessible in the same manner and allow dot escaping. Additionally, the replaced keys may receive any valid JSON value, including objects.
String | String[]Specifies the name/s of a shareable configuration.
This package shares a configuration with common settings that can be extended from clean-package/common.
(hasChanged: boolean, config: CompiledConfig) => voidpackage.json has been cleaned, supplied with an indication as to whether there were changes and the compiled configuration.
(hasChanged: boolean, config: CompiledConfig) => voidpackage.json has been restored, supplied with an indication as to whether there were changes and the compiled configuration.`
clean-package [[
where
-c, --config
-e, --extends
-i, --indent
-rm, --remove
--remove-add
-r, --replace
--replace-add
--print-config Print the combined configuration without executing command.
-v, --version Print the version number
`
`
clean-package restore [[
alias: r
where
-c, --config
-e, --extends
--print-config Print the combined configuration without executing command.
`
Should you desire, it is also possible to interface this package through code. Simply import the package like any other.
`ts`
import { load, clean, restore, version } from 'clean-package';
If you're integrating clean-package into the NPM lifecycle, removing all the package.json scripts with clean-package will also remove them from the current execution. This is just how NPM works.
For example, this configuration will remove the postpack script before it is ever requested by npm pack or npm publish, thereby effectively removing the event from the executing lifecycle.
`json`
{
"scripts": {
"prepack": "clean-package",
"postpack": "clean-package restore"
},
"clean-package": {
"remove": [
"clean-package",
"scripts"
]
}
}
There are multiple ways to work around this (more than are offered here). One solution might be to manually run the command with npx clean-package restore. Another might be to define a custom script that would call pack and clean-package in sequence:
`json``
{
"scripts": {
"prepack": "clean-package",
"new:pack": "npm pack && clean-package restore",
"new:publish": "npm publish && clean-package restore"
}
}