npm init -y won't work on default .node-red folder

[Noddegamrah]

When trying to commit, node-red-contrib-git-ui/git/git-ui/git-ui.js will delete the package.json file (line 14) and run "npm init -y" (line 23) taking all the default values.

Running on a Raspberry Pi, for example, the default node-red home folder is /home/pi/.node-red/ and the name value in this case is ".node-red", returning an exception and making it impossible to commit from the default folder because of the dot included in the name.

You end up without package.json file(!) and unable to commit any changes.

Maybe the package.json file should be backed up and restored if "npm init -y" fails. And maybe the package.json file should be generated in a different way to avoid issues since "npm init" will not accept any configuration parameters ----> npm init [-f|--force|-y|--yes]

[PotOfCoffee2Go]

I also had run into similar issues with package.json being deleted/changed. I create and maintain entries in package.json independently from node-red-contrib-git-ui, so I commented out the delete/npm init -y code from git/git-ui/git-ui.js. See commit.

Is there a reason that package.json needs to be rebuilt on each git-ui commit?

[ifeora-emeka]

Go to this link and copy and paste the code into your command line https://docs.npmjs.com/troubleshooting/if-your-npm-is-broken let me know if it helps

[PotOfCoffee2Go]

npm is working correctly - the problem is that node-red-contrib-git-ui is deleting and rebuilding the package.json on each commit - which works fine unless you made any changes to package.json (which are lost when it is rebuilt).

I do not see any situation which node-red-contrib-git-ui should play around with package.json - just leave it alone and all works great ;) My mod changes the behavior - package.json is not deleted nor rebuilt by node-red-contrib-git-ui.

I have been using with my changes for quite a while now without issues. Am I missing something? Is there a reason that package.json needs to be rebuilt on each git-ui commit?