# package-changed

> Tells you whether or not dependencies in package.json have been changed.

Latest version **3.0.0** (published 2023-03-24) · ISC license · 0 weekly downloads

## Install

```sh
npm install package-changed
pnpm add package-changed
yarn add package-changed
bun add package-changed
```

Provides the command `package-changed`.

## Health

**Score 20/100 (F)** — status: abandoned.

Positive: has types; no vulnerabilities.

Warnings: low downloads; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 3.0.0 |
| Published | 2023-03-24 |
| First published | 2020-11-07 |
| Weekly downloads | 0 |
| License | ISC |
| TypeScript types | bundled |
| Module format | CommonJS |
| Dependencies | 1 |
| Unpacked size | 137.3 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 15 |
| Author | Thomas Dekiere |
| Maintainers | thdk |
| Keywords | npm, install, modified, changed, changes, package, dependencies, devDepencies, package, hash |

## Links

- npm: https://www.npmjs.com/package/package-changed
- Repository: https://github.com/thdk/package-changed
- Homepage: https://github.com/thdk/package-changed#readme
- Issues: https://github.com/thdk/package-changed/issues
- npm.io page: https://npm.io/package/package-changed

## Dependencies (1)

- [commander](https://npm.io/package/commander.md) ^6.2.0

## Alternatives

- [@gemini-wallet/core](https://npm.io/package/@gemini-wallet/core.md) — 515.6K weekly downloads
- [utility](https://npm.io/package/utility.md) — 416.6K weekly downloads
- [@primno/dpapi](https://npm.io/package/@primno/dpapi.md) — 7.2K weekly downloads
- [pi-readseek](https://npm.io/package/pi-readseek.md) — 3.7K weekly downloads
- [@emilia-protocol/verify](https://npm.io/package/@emilia-protocol/verify.md) — 1.1K weekly downloads

## Recent versions

- 3.0.0 (latest) — 2023-03-24
- 2.0.0 — 2023-01-30
- 1.9.0 — 2021-12-20
- 1.8.0 — 2021-12-18
- 1.7.0 — 2021-05-11
- 1.6.0 — 2021-02-27
- 1.5.3 — 2020-11-19
- 1.5.2 — 2020-11-19
- 1.5.1 — 2020-11-09
- 1.5.0 — 2020-11-08
- 1.4.0 — 2020-11-08
- 1.3.3 — 2020-11-08
- 1.3.2 — 2020-11-08
- 1.3.1 — 2020-11-08
- 1.3.0 — 2020-11-08
- … 9 more at https://npm.io/package/package-changed/versions

## README

# package-changed

This package is a quick and easy way of figuring out whether or not `package.json` has been modified.

It contains mainly code extracted from [install-changed](https://github.com/ninesalt/install-changed).

`install-changed` will run `npm install` when dependencies have changed. `package-changed` also provides this functionality. However, it does give you **more control** on what should happen when dependencies in your package.json file have changed.

## Install

You can find this package on `npm` and can install it with:

`npm install package-changed`

However, you can use it without having to install it using `npx`:

`npx package-changed`

## Documentation

### CLI

Use **package-changed** simply by running following from your project root:

`npx package-changed`

This is, in fact, a shorthand for the following commands:

`npx package-changed run "npm install"`

or if you have an **environmental variable** `CI` with value set to `true` then it will run:

`npx package-changed run "npm ci"`

However, using the `run` command you can specify any command which you want to run in case your dependencies have changed since the last run.

```
npx package-changed run "echo 'Run any command when your package has changed'"
```

#### All CLI options

**package-changed**

```
Options:
  --cwd [cwd]                 Current working directory.
  --hash-filename [filename]  Filename where hash of dependencies will be written to
  --lockfile                  Include package versions from package-lock.json in hash
  --no-hash-file              Skip writing new hash to .packagehash file
  -h, --help                  display help for command

Commands:
  run [command]
  install [options]
  help [command]              display help for command
```

**package-changed install**

```
Usage: package-changed install [options]

Options:
  --ci        Run 'npm ci' instead of 'npm i'. Even when package is not changed. Default when env.CI=true
  -r, --registry <registry>  npm registry url to use
  -h, --help  display help for command
```

**package-changed run**

```
Usage: package-changed run [options] [command]

Options:
  -h, --help  display help for command
```

#### Use git hooks to run **package-changed** automatically


**package-changed** can be run automatically with git hooks, for example: when switching branches. [Husky](https://github.com/typicode/husky) is a popular choice for configuring git hooks.

With Husky installed:

```shell
npx husky add .husky/post-checkout "npx --no package-changed"
npx husky add .husky/post-merge "npx --no package-changed"
npx husky add .husky/post-rebase "npx --no package-changed"
```


### Javascript API

```javascript
isPackageChanged(
  options?: PackageChangedOptions,
  callback?: (result: PackageChangedCallbackResult) => Promise<boolean>,
): Promise<PackageChangedResult>;
```

#### Example usage
```javascript
const {
  isPackageChanged
} = require('package-changed')

// run with default options
const {
  isChanged,
} = isPackageChanged();

// or run with custom options
const {
  isChanged,
  writeHash,
} = await isPackageChanged({
  hashFilename: '.packagehash',
});

if (isChanged) {
  // dependencies in your package.json have changed since last run
  ...
  // call writeHash to write the latest package hash to your disk
  writeHash();
}

// or use the callback argument
isPackageChanged(
  undefined, // using default options
  ({isChanged}) => {
    // ...

    return true; // or false if you don't want the hash to be written
  },
);
```

**PackageChangedOptions**
| Property      | Type    | Description                                             | Required | Default          |
| ------------- | ------- | ------------------------------------------------------- | -------- | ---------------- |
| cwd           | string  | Current working directory                               | false    | `process.cwd()`  |
| hashFilename  | string  | Filename where hash of dependencies will be written to. | false    | `'.packagehash'` |
| lockfile      | boolean | Include package-lock.json content in hash.              | false    | `false`          |
| noHashFile    | boolean | Skip writing new hash to .packagehash file.              | false    | `false`          |


**PackageChangedCallbackResult**
| Property  | Type                | Description                                                                       |
| --------- | ------------------- | --------------------------------------------------------------------------------- |
| isChanged | boolean             | Filename where hash of dependencies will be written to.                           |
| hash      | string              | The hash for the current listed dependencies in `package.json`                    |
| oldHash   | string \| undefined | The hash used to compare newHash with. `undefined` if no previous hash was found. |


**PackageChangedResult**
| Property  | Type                | Description                                                                       |
| --------- | ------------------- | --------------------------------------------------------------------------------- |
| isChanged | boolean             | Filename where hash of dependencies will be written to.                           |
| hash      | string              | The hash for the current listed dependencies in `package.json`                    |
| oldHash   | string \| undefined | The hash used to compare newHash with. `undefined` if no previous hash was found. |
| writeHash | function            | Function which needs to be called after the cache has been succesfully restored.  |

---
_Source: https://npm.io/package/package-changed · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._