You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
When running commands from
scripts
, any NPM warnings seem to breakcz
prompts.For example, running
npm run commit
(which runsgit-cz
) triggers some NPM warnings in my environment that then break thecz
prompts. The same warnings are triggered bynpx cz
but the prompt continues to work normally. Usingyarn
to run thescript
(yarn run commit
) also works normally.The given error is caused by the Flatpak
vscodium
environment. The error is:I can't remove the entry
tmp
in/app/etc/npmrc
given that file is read-only in thevscodium
Flatpak.For now it's easy to use
npx git-cz
oryarn run git-cz
. This may not even be a direct issue withgit-cz
but insteadnpm
,node
, or my shell environment. But I thought I'd share in case anyone else comes across this annoyance.The text was updated successfully, but these errors were encountered: