# Problem with npm

**URL:** <https://discourse.nodered.org/t/problem-with-npm/75650>\
**Category:** General\
**Created:** [23 February 2023 17:31 UTC](https://discourse.nodered.org/t/problem-with-npm/75650 "2023-02-23T17:31:06Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![demokedes](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/demokedes/32/19082_2.png) [@demokedes](https://discourse.nodered.org/u/demokedes)\
**Post date:** [23 February 2023 17:31 UTC](https://discourse.nodered.org/t/problem-with-npm/75650/1 "2023-02-23T17:31:06Z")

</div>

Dear all,  
I am using node-red for a while already. Today I was doing something outside of node-red on the server where node-red is running. As a consequence, server became unresponsive. I forced restart of virtual machine. After that node-red started sucesfuly, but when I try to install new pallete, I get an error:

```auto
 npm install node-red-contrib-openhab3

up to date, audited 2009 packages in 17s

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

94 vulnerabilities (3 low, 25 moderate, 52 high, 14 critical)

To address all issues, run:
  npm audit fix

Run `npm audit` for details.

```

Even if I want to remove one of the installed pallets, I get an error. I think something is wrong with npm. What is the easiest way to solve it. If it is complicated, I can even do restore a backup snapshot from few days ago.  
What are you suggesting me?

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [23 February 2023 17:38 UTC](https://discourse.nodered.org/t/problem-with-npm/75650/2 "2023-02-23T17:38:30Z")

</div>

There are no errors in that output - only warnings. The npm install has completed successfully.

The warnings are around potentially out of date modules you have installed. Some may be node-red modules, but they are more likely to be modules used by the nodes you have installed.

Running `npm audit fix` can be a bit risky as it will try to update modules without necessarily knowing the impact that will have on the modules that depend on them.

---

<div class="post-metadata">

**Author:** ![demokedes](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/demokedes/32/19082_2.png) [@demokedes](https://discourse.nodered.org/u/demokedes)\
**Post date:** [23 February 2023 17:43 UTC](https://discourse.nodered.org/t/problem-with-npm/75650/3 "2023-02-23T17:43:57Z")

</div>

Hm, I tried to install it through UI and tells me, it was not successful. Log gives me that:

```auto
2023-02-23T17:42:45.180Z Install : node-red-contrib-openhab3 1.4.9

2023-02-23T17:42:45.478Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-openhab3@1.4.9
2023-02-23T17:42:45.838Z [err] npm
2023-02-23T17:42:45.838Z [err]  
2023-02-23T17:42:45.838Z [err] WARN
2023-02-23T17:42:45.839Z [err]  
2023-02-23T17:42:45.839Z [err] config
2023-02-23T17:42:45.839Z [err] production Use `--omit=dev` instead.
2023-02-23T17:42:49.967Z [err] npm
2023-02-23T17:42:49.968Z [err]  
2023-02-23T17:42:49.968Z [err] ERR!
2023-02-23T17:42:49.968Z [err]  
2023-02-23T17:42:49.968Z [err] code
2023-02-23T17:42:49.968Z [err] ENOTEMPTY
2023-02-23T17:42:49.968Z [err] npm
2023-02-23T17:42:49.968Z [err]  
2023-02-23T17:42:49.968Z [err] ERR!
2023-02-23T17:42:49.968Z [err]  
2023-02-23T17:42:49.968Z [err] syscall
2023-02-23T17:42:49.969Z [err] rename
2023-02-23T17:42:49.969Z [err] npm
2023-02-23T17:42:49.969Z [err]  
2023-02-23T17:42:49.969Z [err] ERR!
2023-02-23T17:42:49.969Z [err]  
2023-02-23T17:42:49.969Z [err] path
2023-02-23T17:42:49.969Z [err] /home/demokedes/.node-red/node_modules/socks
2023-02-23T17:42:49.969Z [err] npm
2023-02-23T17:42:49.969Z [err]  
2023-02-23T17:42:49.969Z [err] ERR!
2023-02-23T17:42:49.969Z [err]  
2023-02-23T17:42:49.969Z [err] dest
2023-02-23T17:42:49.969Z [err] /home/demokedes/.node-red/node_modules/.socks-pPb85qSE
2023-02-23T17:42:49.969Z [err] npm
2023-02-23T17:42:49.969Z [err]  
2023-02-23T17:42:49.969Z [err] ERR!
2023-02-23T17:42:49.970Z [err]  
2023-02-23T17:42:49.970Z [err] errno
2023-02-23T17:42:49.970Z [err] -39
2023-02-23T17:42:49.971Z [err] npm
2023-02-23T17:42:49.971Z [err]  
2023-02-23T17:42:49.971Z [err] ERR!
2023-02-23T17:42:49.971Z [err] ENOTEMPTY: directory not empty, rename '/home/demokedes/.node-red/node_modules/socks' -> '/home/demokedes/.node-red/node_modules/.socks-pPb85qSE'
2023-02-23T17:42:49.972Z [err] 
2023-02-23T17:42:49.972Z [err] npm
2023-02-23T17:42:49.972Z [err]  
2023-02-23T17:42:49.972Z [err] ERR!
2023-02-23T17:42:49.972Z [err] A complete log of this run can be found in:
2023-02-23T17:42:49.972Z [err] npm
2023-02-23T17:42:49.972Z [err]  
2023-02-23T17:42:49.972Z [err] ERR!
2023-02-23T17:42:49.972Z [err] /home/demokedes/.npm/_logs/2023-02-23T17_42_45_798Z-debug-0.log
2023-02-23T17:42:49.979Z rc=217

```

[2023-02-23T17\_42\_45\_798Z-debug-0.log](https://discourse.nodered.org/uploads/short-url/zndWeOVpBUiBwF0spvZZsyFAQM4.log) (63.8 KB)

---

<div class="post-metadata">

**Author:** ![demokedes](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/demokedes/32/19082_2.png) [@demokedes](https://discourse.nodered.org/u/demokedes)\
**Post date:** [23 February 2023 20:52 UTC](https://discourse.nodered.org/t/problem-with-npm/75650/4 "2023-02-23T20:52:14Z")

</div>

I think I somehow solved it. I don't know what exactly helped me, because I did several things, but it is working now.

---

<div class="post-metadata">

**Author:** ![JuanSchwab](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@JuanSchwab](https://discourse.nodered.org/u/JuanSchwab)\
**Post date:** [27 March 2023 01:17 UTC](https://discourse.nodered.org/t/problem-with-npm/75650/5 "2023-03-27T01:17:45Z")

</div>

> [@demokedes](#):
>
> I am using node-red for a while already. Today I was doing something outside of node-red on the server where node-red is running. As a consequence, server became unresponsive. I forced restart of virtual machine. After that node-red started sucesfuly, but when I try to install new pallete, I get an error:
> 
> > ****
> >
> > I tried it but failed. If you're currently searching for essay topics, I would like to suggest a website that could be of great help to you. By visiting [https://writinguniverse.com/classification-essay-topics/](https://writinguniverse.com/classification-essay-topics/) you can browse through a wide selection of essay topics that are specifically designed to help you complete your essay writing assignments.
> 
> ```auto
> npm install node-red-contrib-openhab3
> 
> up to date, audited 2009 packages in 17s
> 
> 79 packages are looking for funding
> run `npm fund` for details
> 
> 94 vulnerabilities (3 low, 25 moderate, 52 high, 14 critical)
> 
> To address all issues, run:
> npm audit fix
> 
> Run `npm audit` for details.
> 
> ```
> 
> Even if I want to remove one of the installed pallets, I get an error. I think something is wrong with npm. What is the easiest way to solve it. If it is complicated, I can even do restore a backup snapshot from few days ago.  
> What are you suggesting me?

Edit: I tried it but failed.

---

<div class="post-metadata">

**Author:** ![tree-frog](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tree-frog/32/89303_2.png) [@tree-frog](https://discourse.nodered.org/u/tree-frog)\
**Post date:** [27 March 2023 01:44 UTC](https://discourse.nodered.org/t/problem-with-npm/75650/6 "2023-03-27T01:44:27Z")

</div>

Please update us as to what things you did. Details like Windows 10 vs. Linux + Distro. Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [26 May 2023 01:45 UTC](https://discourse.nodered.org/t/problem-with-npm/75650/7 "2023-05-26T01:45:10Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.