The install script always puts all config.pre-git entries as well as scripts.commit into the package.json regardless of whether the user already did configure pre-git. This is not nice: If a user wants to leave out some of those config entries, they are inserted again later, e.g. on a later npm install. Thus with this PR the entries are only written to package.json if there is no config.pre-git key yet in it.
The install script always puts all
config.pre-git
entries as well asscripts.commit
into the package.json regardless of whether the user already did configure pre-git. This is not nice: If a user wants to leave out some of those config entries, they are inserted again later, e.g. on a laternpm install
. Thus with this PR the entries are only written to package.json if there is noconfig.pre-git
key yet in it.