clean-package
clean-package copied to clipboard
roydukkey
Remove configuration keys from 'package.json' before creating an NPM package.
hello there.... clean-package is awesome ❤️❤️❤️ but its extends functionality is broken i'm using config in package.json and i used path as relative to package.json ```json "clean-package": { "extends": "../../../clean-package.config.json",...
Additionally, in order to improve the CLI experience, yargs will be used to allow for creating the `--help` content.
Currently, the spec for the CLI is that the first optional, positional argument is `backup-path`. Then a `source-path` may optionally be specified before `backup-path`. To simplify the API, `source-path` will...
Should be able to target the `package.json` location based on the `process.env.npm_lifecycle_event == 'postpack'`, therefore not requiring any new APIs. However, research needs to be done in order to determine...
# What is the purpose of this Pull Request? It resolves the issue where the types defined in your project cannot be imported. I noticed it when trying to make...
This change will be breaking, but will ultimately be more predictable. It will also make it easier for using `clean-package` for things like ordering `package.json` keys.
For example, peer dependencies can simply be a numeric string (`"1"`, `"2"`, etc.). However, the following code converts such values to numbers (`1`, `2`, etc.). https://github.com/roydukkey/clean-package/blob/a03da14f3c9cb6fae61807ec299bc724d2ecd905/src/clean.ts#L41 At the very least...