Warnings while (re-) installing node-red-contrib-bluelinky

[binderth]

After using the way described in #61 I got the following warnings:

pi@nodered:~ $ npm uninstall node-red-contrib-bluelinky
npm WARN saveError ENOENT: no such file or directory, open '/home/pi/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm WARN pi No description
npm WARN pi No repository field.
npm WARN pi No README data
npm WARN pi No license field.

audited 299 packages in 7.656s

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

found 8 vulnerabilities (6 moderate, 2 high)
  run `npm audit fix` to fix them, or `npm audit` for details
pi@nodered:~ $ npm install node-red-contrib-bluelinky
npm WARN saveError ENOENT: no such file or directory, open '/home/pi/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm WARN pi No description
npm WARN pi No repository field.
npm WARN pi No README data
npm WARN pi No license field.

+ node-red-contrib-bluelinky@0.0.27
added 2 packages from 3 contributors and audited 301 packages in 10.923s

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

found 9 vulnerabilities (7 moderate, 2 high)
  run `npm audit fix` to fix them, or `npm audit` for details
pi@nodered:~ $ sudo service nodered restart

is this something I have to take a look on?

[PierreLevres]

You don't HAVE to, they are 'only' warnings. If you want to get rid of the warnings, there are a lot of helpful sites how to set up NPM in the correct way. This issue is not related to bluelinky, node-red-contrib-bluelinky, but to the setup of your environment.

[binderth]

ok. all right! It was a vanilla installation of nodred on a dedicated Pi, I'll have a look for what went wrong here!