ENOTEMPTY when installing node from palette since nodered 3.0 (directory not empty)

Colin · 5 August 2022 08:19

Others are encountering this issue too.

[BUG] install global typescript got error: npm ERR! ENOTEMPTY: directory not empty

opened 07:41AM - 26 Nov 21 UTC

Release 8.x Bug Needs Triage

### Is there an existing issue for this? - [X] I have searched the existing iss…ues ### This issue exists in the latest npm version - [X] I am using the latest npm ### Current Behavior ```bash ➜ create-config git:(feat/eslint-init) npm i typescript -g npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /Users/weiran/.npm-global/lib/node_modules/typescript npm ERR! dest /Users/weiran/.npm-global/lib/node_modules/.typescript-ffKYZhoU npm ERR! errno -66 npm ERR! ENOTEMPTY: directory not empty, rename '/Users/weiran/.npm-global/lib/node_modules/typescript' -> '/Users/weiran/.npm-global/lib/node_modules/.typescript-ffKYZhoU' npm ERR! A complete log of this run can be found in: npm ERR! /Users/weiran/.npm/_logs/2021-11-26T07_32_40_759Z-debug.log ``` ### Expected Behavior global typescript installed without error. ### Steps To Reproduce _No response_ ### Environment - npm: 8.1.4 - Node: v17.0.1 - OS: macOS 12.1 - platform: - npm config: ```ini ; copy and paste output from `npm config ls` here ; "user" config from /Users/weiran/.npmrc //git.dian.so/api/v4/packages/npm/:_authToken = (protected) //npm.xiaodiankeji.net/:_authToken = (protected) //registry.npmjs.org/:_authToken = (protected) home = "https://npm.taobao.org" http-proxy = "http://127.0.0.1:8118" https-proxy = "http://127.0.0.1:8118/" init-author-name = "weiran" ; package-lock = true ; overridden by project prefix = "/Users/weiran/.npm-global" proxy = "http://127.0.0.1:8118/" ; "project" config from /Users/weiran/repo/github/create-config/.npmrc package-lock = false ; node bin location = /usr/local/bin/node ; cwd = /Users/weiran/repo/github/create-config ; HOME = /Users/weiran ; Run `npm config ls -l` to show all defaults. ```

github.com/firebase/firebase-tools

npm ERR! ENOTEMPTY: directory not empty, rename '/usr/local/lib/node_modules/firebase-tools'

opened 04:12PM - 23 Mar 22 UTC

closed 06:09PM - 23 Mar 22 UTC

Tom3652

bug

### [REQUIRED] Environment info **firebase-tools:** 10.2.2 **Platform:** macOS ### [REQUIRED] Test case ``` (base) foxtom@MacBook-Pro-de-FoxTom myproject % sudo npm install -g firebase-tools Password: npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /usr/local/lib/node_modules/firebase-tools npm ERR! dest /usr/local/lib/node_modules/.firebase-tools-ENG41nb9 npm ERR! errno -66 npm ERR! ENOTEMPTY: directory not empty, rename '/usr/local/lib/node_modules/firebase-tools' -> '/usr/local/lib/node_modules/.firebase-tools-ENG41nb9' npm ERR! A complete log of this run can be found in: npm ERR! /Users/foxtom/.npm/_logs/2022-03-23T16_07_07_098Z-debug-0.log ``` ### [REQUIRED] Steps to reproduce ![Capture d’écran 2022-03-23 à 17 09 50](https://user-images.githubusercontent.com/32631467/159744742-379ad819-3e90-4c05-b122-cafd9c430247.png) As asked by the message, run ```sudo npm install -g firebase-tools``` (if you run without `sudo` you will get a permission denied error) ### [REQUIRED] Expected behavior Be able to update the CLI tools. ### [REQUIRED] Actual behavior ``` npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /usr/local/lib/node_modules/firebase-tools npm ERR! dest /usr/local/lib/node_modules/.firebase-tools-ENG41nb9 npm ERR! errno -66 npm ERR! ENOTEMPTY: directory not empty, rename '/usr/local/lib/node_modules/firebase-tools' -> '/usr/local/lib/node_modules/.firebase-tools-ENG41nb9' npm ERR! A complete log of this run can be found in: npm ERR! /Users/foxtom/.npm/_logs/2022-03-23T16_07_07_098Z-debug-0.log ``` I have to delete the directory manually to fix this and i would prefer to not do this by myself

github.com/homebridge/homebridge

Update to v4.45.0 failed

opened 12:52AM - 25 May 22 UTC

closed 04:04AM - 25 May 22 UTC

rupil10

question

### Current Situation When I updated to v4.43.3 I received a similar error to b…elow. I was able to get around it by updating it via terminal from some guide that I found online however just trying to update to v4.45.0 the same thing has happened again. Am I going to have to keep forcing it to happen via terminal or is there someway that I can fix this issue so that I can just update using the UI. I really don't understand the terminal side of things in great detail and feel like I might break my installation if I mess with it too much. USER: pi DIR: /usr/local CMD: sudo -E -n npm install -g homebridge-config-ui-x@latest npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /usr/local/lib/node_modules/homebridge-config-ui-x npm ERR! dest /usr/local/lib/node_modules/.homebridge-config-ui-x-3gtnOIj4 npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/usr/local/lib/node_modules/homebridge-config-ui-x' -> '/usr/local/lib/node_modules/.homebridge-config-ui-x-3gtnOIj4' npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2022-05-24T22_06_22_459Z-debug.log Cleaning up npm cache, please wait... npm cache cleared, please try updating homebridge-config-ui-x again. Command failed. Please review log for details. Thanks ### Logs ```markdown none ``` ### Configuration ```json none ``` ### Environment - OS: - Software: - Node: - npm: ### Process Supervisor hb-service ### Additional Context _No response_

and numerous others, but so far have not found any information about what might be triggering it.

Topic		Replies	Views
Cannot install nodes via palette manager General	7	272	4 January 2023
Nodered no npm Update possible General	5	770	29 September 2022
Node updates fail using Manage Palette General	4	274	16 November 2022
Can't install palette on docker stack General	1	438	27 February 2022
Update Problem with node-red-contrib-netatmo 0.3.0 General	3	448	31 January 2022

ENOTEMPTY when installing node from palette since nodered 3.0 (directory not empty)

Related Topics