commitizen / commitizen/cz-cli

NPM warning breaks `cz` prompts when using `scripts` entry

Open
#964 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
17.5k
Forks
566
Avg merge
8h 16m
Merged PRs (30d)
1

Description

When running commands from `scripts`, any NPM warnings seem to break `cz` prompts.

For example, running `npm run commit` (which runs `git-cz`) triggers some NPM warnings in my environment that then break the `cz` prompts. The same warnings are triggered by `npx cz` but the prompt continues to work normally. Using `yarn` to run the `script` (`yarn run commit`) also works normally.

The given error is caused by the Flatpak `vscodium` environment. The error is:

```bash
npm WARN config tmp This setting is no longer used. npm stores temporary files in a special
npm WARN config location in the cache, and they are managed by
npm WARN config [`cacache`](http://npm.im/cacache).
```

I can't remove the entry `tmp` in `/app/etc/npmrc` given that file is read-only in the `vscodium` Flatpak.

For now it's easy to use `npx git-cz` or `yarn run git-cz`. This may not even be a direct issue with `git-cz` but instead `npm`, `node`, or my shell environment. But I thought I'd share in case anyone else comes across this annoyance.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.