When running `package-changed run` in a CI environment, hash is not created

[TheRealWaldo]

The hash is never created in an environment with the CI env var set to true:

❯ CI=true npx package-changed run 'npm ci --ignore-scripts'

added 910 packages, and audited 1148 packages in 3m

196 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
❯ ls -al .packagehash
ls: cannot access '.packagehash': No such file or directory

This is undesirable as it causes problems installing hooks and fires multiple times when used in npm 'pre' commands .

Is there a way to force it to create the hash?

[thdk]

Package-changed was never meant to run in a CI environment.

See also this from the docs:

Options: --ci Run 'npm ci' instead of 'npm i'. Even when package is not changed. Default when env.CI=true

Can you tell me why you would like to run it as such?

[paraself]

It's useful when some deps are changed and artifacts are generated based on what deps are used.