# Npm install issues?

**URL:** <https://discourse.nodered.org/t/npm-install-issues/67561>\
**Category:** General\
**Created:** [10 September 2022 18:27 UTC](https://discourse.nodered.org/t/npm-install-issues/67561 "2022-09-10T18:27:00Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sean-McG](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sean-mcg/32/54677_2.png) [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)\
**Post date:** [10 September 2022 18:27 UTC](https://discourse.nodered.org/t/npm-install-issues/67561/1 "2022-09-10T18:27:00Z")

</div>

Trying to move node red to a new rpi. Installed node red and tested OK  
copied over flows package,json etc and ran npm install to insall missing nodes but no luck any ideas please ?

```auto
pi@pi-server:~/.node-red $ npm install
npm WARN skipping integrity check for git dependency ssh://git@github.com/agsh/onvif.git
npm WARN skipping integrity check for git dependency ssh://git@github.com/bartbutenaers/node-red-contrib-ui-multistate-switch.git
npm WARN skipping integrity check for git dependency ssh://git@github.com/kevinGodell/node-red-contrib-ui-mp4frag.git
npm WARN skipping integrity check for git dependency ssh://git@github.com/kevinGodell/node-red-contrib-mp4frag.git
npm WARN skipping integrity check for git dependency ssh://git@github.com/kevinGodell/node-red-contrib-ffmpeg-spawn.git
npm WARN deprecated loadash@1.0.0: Package is unsupport. Please use the lodash package instead.
npm WARN deprecated ini@1.3.5: Please update to ini >=1.3.6 to avoid a prototype pollution issue
npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/req uest/issues/3142
npm WARN deprecated har-validator@5.1.3: this library is no longer supported
npm WARN deprecated mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/31 42
npm WARN deprecated flat@4.1.0: Fixed a prototype pollution security issue in 4.1.0, please upgrade to ^4.1.1 or ^5.0.1.
npm WARN deprecated debug@4.2.0: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.2.0: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated socks@1.1.10: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
npm WARN deprecated debug@3.2.6: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@3.2.6: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@3.2.6: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@3.2.6: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@3.2.6: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@3.2.6: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@3.2.6: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated multer@1.4.2: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at l east Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release l ine, whilst maintaining compatibility with Node.js 0.10.
npm WARN deprecated formidable@1.2.2: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https:/ /v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.3.2: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https:/ /v8.dev/blog/math-random for details.
npm WARN deprecated node-red-contrib-anolog-to-digital-converter-raspberry-pi@0.4.26: WARNING: This project has been replaced with node-red-contrib-ads1x15_i2c
npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated request@2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated bcrypt@3.0.6: versions < v5.0.0 do not handle NUL in passwords properly
npm WARN deprecated node-pre-gyp@0.12.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve up dates in the future
npm WARN deprecated node-pre-gyp@0.11.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve up dates in the future
npm WARN deprecated superagent@3.8.3: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (EN OENT on attach()), and all tests are now passing. See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>.
npm WARN deprecated core-js@3.15.2: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detecti on in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actu al version of core-js.
npm WARN deprecated @vladmandic/face-api@1.4.1: deprecated
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/node-red-contrib-date/-/node-red-contrib-date-0.0.2.tgz - Not found
npm ERR! 404
npm ERR! 404 'node-red-contrib-date@https://registry.npmjs.org/node-red-contrib-date/-/node-red-contrib-date-0.0.2.tgz' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:

```

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [10 September 2022 19:15 UTC](https://discourse.nodered.org/t/npm-install-issues/67561/2 "2022-09-10T19:15:34Z")

</div>

Can you show us your package.json

Have you restored package-lock.json? If so then try removing that and the node\_modules directory and try again.

---

<div class="post-metadata">

**Author:** ![paulkeates](https://avatars.discourse-cdn.com/v4/letter/p/9de053/32.png) [@paulkeates](https://discourse.nodered.org/u/paulkeates)\
**Post date:** [10 September 2022 20:08 UTC](https://discourse.nodered.org/t/npm-install-issues/67561/3 "2022-09-10T20:08:48Z")

</div>

Hi,

Does the new rpi have Git installed? Are you using the Project feature or a single Flow?

Cheers,

Paul

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [10 September 2022 20:15 UTC](https://discourse.nodered.org/t/npm-install-issues/67561/4 "2022-09-10T20:15:18Z")

</div>

> [@Sean-McG](#):
>
> `Not Found - GET https://registry.npmjs.org/node-red-contrib-date/-/node-red-contrib-date-0.0.2.tgz - Not found`

It appears that node-red-contrib-date does not exist.

---

<div class="post-metadata">

**Author:** ![Sean-McG](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sean-mcg/32/54677_2.png) [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)\
**Post date:** [10 September 2022 22:45 UTC](https://discourse.nodered.org/t/npm-install-issues/67561/5 "2022-09-10T22:45:03Z")

</div>

> [@paulkeates](#):
>
> Does the new rpi have Git installed? Are you using the Project feature or a single Flow?

git version 2.30.2  
1 flow, no projects

---

<div class="post-metadata">

**Author:** ![Sean-McG](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sean-mcg/32/54677_2.png) [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)\
**Post date:** [10 September 2022 23:04 UTC](https://discourse.nodered.org/t/npm-install-issues/67561/6 "2022-09-10T23:04:13Z")

</div>

> [@Colin](#):
>
> Can you show us your package.json

```auto
{
  "name": "node-red-project",
  "description": "A Node-RED Project",
  "version": "0.0.1",
  "dependencies": {
    "canvas": "^2.6.1",
    "i2c-bus": "^4.0.7",
    "jsonata": "^1.8.6",
    "moment": "^2.29.2",
    "node-red-contrib-aggregator": "~1.5.0",
    "node-red-contrib-alarm": "~1.3.0",
    "node-red-contrib-alexa-home-skill": "~0.1.19",
    "node-red-contrib-alexa-remote2-applestrudel": "~5.0.20",
    "node-red-contrib-anolog-to-digital-converter-raspberry-pi": "~0.4.26",
    "node-red-contrib-arp": "0.0.2",
    "node-red-contrib-bigtimer": "~2.8.2",
    "node-red-contrib-blockly": "~2.0.0",
    "node-red-contrib-bool-gate": "~1.0.2",
    "node-red-contrib-browser-utils": "0.0.10",
    "node-red-contrib-camerapi": "0.0.39",
    "node-red-contrib-chroma": "0.0.3",
    "node-red-contrib-collector": "0.0.1",
    "node-red-contrib-colorspace": "~1.0.2",
    "node-red-contrib-combine": "~1.8.1",
    "node-red-contrib-compass": "~1.0.1",
    "node-red-contrib-config": "~1.2.1",
    "node-red-contrib-countdown-2": "~1.4.2",
    "node-red-contrib-covid19": "~2.0.1",
    "node-red-contrib-cpu": "0.0.4",
    "node-red-contrib-cron-plus": "~1.5.7",
    "node-red-contrib-dashboard-average-bars": "0.0.6",
    "node-red-contrib-dashboard-bar-chart-data": "~0.9.8",
    "node-red-contrib-dashboard-sum-bars": "0.0.1",
    "node-red-contrib-dsm": "~0.14.1",
    "node-red-contrib-eztimer": "~1.2.7",
    "node-red-contrib-facial-recognition": "~0.30.105",
    "node-red-contrib-ffmpeg-spawn": "github:kevinGodell/node-red-contrib-ffmpeg-spawn",
    "node-red-contrib-google-calendar": "~0.1.5",
    "node-red-contrib-googlehome": "0.0.15",
    "node-red-contrib-hikvision-ultimate": "~1.0.64",
    "node-red-contrib-image-output": "~0.6.3",
    "node-red-contrib-influxdb": "~0.6.1",
    "node-red-contrib-jsontohtml": "~1.0.2",
    "node-red-contrib-match": "~1.0.2",
    "node-red-contrib-merge": "~0.1.1",
    "node-red-contrib-moment": "~4.0.0",
    "node-red-contrib-mp4frag": "github:kevinGodell/node-red-contrib-mp4frag",
    "node-red-contrib-multifeed-parser": "0.0.3",
    "node-red-contrib-multipart-stream-decoder": "0.0.4",
    "node-red-contrib-mytimeout": "~3.2.2",
    "node-red-contrib-onvif-nodes": "0.0.1-beta.7",
    "node-red-contrib-os": "~0.2.1",
    "node-red-contrib-pi-hole": "0.0.3",
    "node-red-contrib-pixelit": "~0.3.14",
    "node-red-contrib-play-audio": "^2.5.0",
    "node-red-contrib-ramp-thermostat": "~0.8.3",
    "node-red-contrib-ring-buffer": "~0.10.0",
    "node-red-contrib-rive": "~1.1.0",
    "node-red-contrib-rpi-shutdown": "0.0.2",
    "node-red-contrib-samsung-tv-control": "~1.3.15",
    "node-red-contrib-satellites": "~0.7.5",
    "node-red-contrib-sequencer": "~1.0.0",
    "node-red-contrib-simple-message-queue": "~0.2.8",
    "node-red-contrib-simpletime": "~2.10.4",
    "node-red-contrib-skyremote-new": "~0.1.2",
    "node-red-contrib-smartswitch": "0.0.1",
    "node-red-contrib-socketio": "~1.1.0",
    "node-red-contrib-string": "~1.0.0",
    "node-red-contrib-sun-position": "~2.1.1",
    "node-red-contrib-tasmota": "~0.9.12",
    "node-red-contrib-telegrambot": "~14.1.0",
    "node-red-contrib-time-range-switch": "~1.1.2",
    "node-red-contrib-timeout": "~1.1.5",
    "node-red-contrib-timeouttrigger": "0.0.3",
    "node-red-contrib-timerswitch": "~1.4.0",
    "node-red-contrib-ui-artless-gauge": "~0.3.11",
    "node-red-contrib-ui-contextmenu": "~2.0.1",
    "node-red-contrib-ui-iro-color-picker": "~0.1.6",
    "node-red-contrib-ui-led": "~0.4.11",
    "node-red-contrib-ui-level": "~0.1.46",
    "node-red-contrib-ui-media": "~1.2.0",
    "node-red-contrib-ui-mp4frag": "github:kevinGodell/node-red-contrib-ui-mp4frag",
    "node-red-contrib-ui-multistate-switch": "github:bartbutenaers/node-red-contrib-ui-multistate-switch",
    "node-red-contrib-ui-state-trail": "~0.4.4",
    "node-red-contrib-ui-svg": "~2.3.1",
    "node-red-contrib-ui-time-scheduler": "~1.17.2",
    "node-red-contrib-ui-value-trail": "~0.2.3",
    "node-red-contrib-uk-national-rail": "~0.1.4",
    "node-red-contrib-unit-converter": "0.0.2",
    "node-red-contrib-vcgencmd": "~1.0.3",
    "node-red-contrib-virtual-smart-home": "~2.14.0",
    "node-red-contrib-watt2kwh": "~0.1.2",
    "node-red-contrib-web-worldmap": "~2.29.0",
    "node-red-contrib-wled": "0.0.4",
    "node-red-contrib-wled3": "~2.5.1",
    "node-red-contrib-xterm": "~1.0.1",
    "node-red-dashboard": "~3.1.7",
    "node-red-node-annotate-image": "~0.1.2",
    "node-red-node-base64": "~0.3.0",
    "node-red-node-darksky": "~0.1.19",
    "node-red-node-dropbox": "~1.1.1",
    "node-red-node-email": "~1.17.0",
    "node-red-node-pi-gpio": "^2.0.5",
    "node-red-node-ping": "^0.3.1",
    "node-red-node-random": "^0.4.0",
    "node-red-node-serialport": "^1.0.1",
    "node-red-node-smooth": "^0.1.2",
    "node-red-node-suncalc": "~1.0.1",
    "node-red-node-tail": "~0.3.2",
    "node-red-node-twitter": "~1.2.0",
    "node-red-node-ui-iframe": "~0.2.1",
    "node-red-node-ui-list": "~0.3.6",
    "node-red-node-ui-table": "~0.4.3",
    "node-red-node-ui-webcam": "~0.4.0",
    "node-red-node-wol": "~0.2.0",
    "node-red-nodes": "^0.1.0",
    "typescript": "^4.5.5"
  }
}

```

Should say that I moved from 32bit to 64bit OS.  
Also removed package-lock.json and the node\_modules directory, and deleted the node-red-contrib-date from package.json.

```auto
pi@pi-server:~/.node-red $ npm install
npm WARN deprecated loadash@1.0.0: Package is unsupport. Please use the lodash p ackage instead.
npm WARN deprecated request-promise-native@1.0.9: request-promise-native has bee n deprecated because it extends the now deprecated request package, see https:// github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated mkdirp@0.5.4: Legacy versions of mkdirp are no longer suppor ted. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated b ecause it extends the now deprecated request package, see https://github.com/req uest/request/issues/3142
npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated formidable@1.2.6: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm WARN deprecated socks@1.1.10: If using 2.x branch, please upgrade to at leas t 2.1.6 to avoid a serious bug with socket data flow and an import issue introdu ced in 2.1.0
npm WARN deprecated socks@1.1.10: If using 2.x branch, please upgrade to at leas t 2.1.6 to avoid a serious bug with socket data flow and an import issue introdu ced in 2.1.0
npm WARN deprecated debug@3.2.6: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 hav e a low-severity ReDos regression when used in a Node.js environment. It is reco mmended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/iss ues/797)
npm WARN deprecated multer@1.4.2: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you n eed support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibilit y with Node.js 0.10.
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older v ersions may use Math.random() in certain circumstances, which is known to be pro blematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older v ersions may use Math.random() in certain circumstances, which is known to be pro blematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated node-red-contrib-anolog-to-digital-converter-raspberry-pi@0. 4.26: WARNING: This project has been replaced with node-red-contrib-ads1x15_i2c
npm WARN deprecated request@2.88.0: request has been deprecated, see https://git hub.com/request/request/issues/3142
npm WARN deprecated request@2.88.2: request has been deprecated, see https://git hub.com/request/request/issues/3142
npm WARN deprecated bcrypt@3.0.6: versions < v5.0.0 do not handle NUL in passwor ds properly
npm WARN deprecated node-pre-gyp@0.12.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped p ackage will recieve updates in the future
npm WARN deprecated superagent@3.8.3: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem erro rs not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at <https://github.com/visionmedia/superagent /releases>.
npm ERR! code 1
npm ERR! path /home/pi/.node-red/node_modules/canvas
npm ERR! command failed
npm ERR! command sh /tmp/install-29f0d072.sh
npm ERR! Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --update-binary --module=/home/pi/.node-red/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/home/pi/.node-red/node_modules/canvas/build/Release --napi_version=8 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v93' (1)
npm ERR! node-pre-gyp info it worked if it ends with ok
npm ERR! node-pre-gyp info using node-pre-gyp@1.0.10
npm ERR! node-pre-gyp info using node@16.17.0 | linux | arm64
npm ERR! node-pre-gyp http GET https://github.com/Automattic/node-canvas/releases/download/v2.10.1/canvas-v2.10.1-node-v93-linux-glibc-arm64.tar.gz
npm ERR! node-pre-gyp ERR! install response status 404 Not Found on https://github.com/Automattic/node-canvas/releases/download/v2.10.1/canvas-v2.10.1-node-v93-linux-glibc-arm64.tar.gz
npm ERR! node-pre-gyp WARN Pre-built binaries not installable for canvas@2.10.1 and node@16.17.0 (node-v93 ABI, glibc) (falling back to source compile with node-gyp)
npm ERR! node-pre-gyp WARN Hit error response status 404 Not Found on https://github.com/Automattic/node-canvas/releases/download/v2.10.1/canvas-v2.10.1-node-v93-linux-glibc-arm64.tar.gz
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using node-gyp@9.0.0
npm ERR! gyp info using node@16.17.0 | linux | arm64
npm ERR! gyp info ok
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using node-gyp@9.0.0
npm ERR! gyp info using node@16.17.0 | linux | arm64
npm ERR! gyp info find Python using Python version 3.9.2 found at "/usr/bin/python3"
npm ERR! gyp info spawn /usr/bin/python3
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
npm ERR! gyp info spawn args 'binding.gyp',
npm ERR! gyp info spawn args '-f',
npm ERR! gyp info spawn args 'make',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args '/home/pi/.node-red/node_modules/canvas/build/config.gypi',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args '/home/pi/.cache/node-gyp/16.17.0/include/node/common.gypi',
npm ERR! gyp info spawn args '-Dlibrary=shared_library',
npm ERR! gyp info spawn args '-Dvisibility=default',
npm ERR! gyp info spawn args '-Dnode_root_dir=/home/pi/.cache/node-gyp/16.17.0',
npm ERR! gyp info spawn args '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',
npm ERR! gyp info spawn args '-Dnode_lib_file=/home/pi/.cache/node-gyp/16.17.0/<(target_arch)/node.lib',
npm ERR! gyp info spawn args '-Dmodule_root_dir=/home/pi/.node-red/node_modules/canvas',
npm ERR! gyp info spawn args '-Dnode_engine=v8',
npm ERR! gyp info spawn args '--depth=.',
npm ERR! gyp info spawn args '--no-parallel',
npm ERR! gyp info spawn args '--generator-output',
npm ERR! gyp info spawn args 'build',
npm ERR! gyp info spawn args '-Goutput_dir=.'
npm ERR! gyp info spawn args ]
npm ERR! Package pixman-1 was not found in the pkg-config search path.
npm ERR! Perhaps you should add the directory containing `pixman-1.pc'
npm ERR! to the PKG_CONFIG_PATH environment variable
npm ERR! No package 'pixman-1' found
npm ERR! gyp: Call to 'pkg-config pixman-1 --libs' returned exit status 1 while in binding.gyp. while trying to load binding.gyp
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: `gyp` failed with exit code: 1
npm ERR! gyp ERR! stack at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:261:16)
npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:513:28)
npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
npm ERR! gyp ERR! System Linux 5.15.61-v8+
npm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--update-binary" "--module=/home/pi/.node-red/node_modules/canvas/build/Release/canvas.node" "--module_name=canvas" "--module_path=/home/pi/.node-red/node_modules/canvas/build/Release" "--napi_version=8" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v93"
npm ERR! gyp ERR! cwd /home/pi/.node-red/node_modules/canvas
npm ERR! gyp ERR! node -v v16.17.0
npm ERR! gyp ERR! node-gyp -v v9.0.0
npm ERR! gyp ERR! not ok
npm ERR! node-pre-gyp ERR! build error
npm ERR! node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --update-binary --module=/home/pi/.node-red/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/home/pi/.node-red/node_modules/canvas/build/Release --napi_version=8 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v93' (1)
npm ERR! node-pre-gyp ERR! stack at ChildProcess.<anonymous> (/home/pi/.node-red/node_modules/@mapbox/node-pre-gyp/lib/util/compile.js:89:23)
npm ERR! node-pre-gyp ERR! stack at ChildProcess.emit (node:events:513:28)
npm ERR! node-pre-gyp ERR! stack at maybeClose (node:internal/child_process:1093:16)
npm ERR! node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
npm ERR! node-pre-gyp ERR! System Linux 5.15.61-v8+
npm ERR! node-pre-gyp ERR! command "/usr/bin/node" "/home/pi/.node-red/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" "--update-binary"
npm ERR! node-pre-gyp ERR! cwd /home/pi/.node-red/node_modules/canvas
npm ERR! node-pre-gyp ERR! node -v v16.17.0
npm ERR! node-pre-gyp ERR! node-pre-gyp -v v1.0.10
npm ERR! node-pre-gyp ERR! not ok

npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2022-09-10T23_07_18_452Z-debug-0.log

```

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [11 September 2022 07:51 UTC](https://discourse.nodered.org/t/npm-install-issues/67561/7 "2022-09-11T07:51:51Z")

</div>

Wow, that is a lot of contrib nodes. Previously it was complaining about node-red-contrib-date, but that doesn't exist and is not in your package.json, so I have no idea where that came from. Now it is complaining about the module canvas, which won't install for me on a (32 bit buster) pi. I see that you have canvas explicitly required in the dependencies in package.json. Do you know why that is there? If you don't need it, or you don't know why it is there, then remove that line and try again.

---

<div class="post-metadata">

**Author:** ![Sean-McG](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sean-mcg/32/54677_2.png) [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)\
**Post date:** [11 September 2022 14:24 UTC](https://discourse.nodered.org/t/npm-install-issues/67561/8 "2022-09-11T14:24:44Z")

</div>

I reinstalled NR and added only the used nodes from the command line 1 by 1. So far so good 🤪

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [11 September 2022 14:37 UTC](https://discourse.nodered.org/t/npm-install-issues/67561/9 "2022-09-11T14:37:47Z")

</div>

It is a good idea to remove contrib nodes that you are not using. You can find them by using Palette Manager in the menu dropdown where it will give the option of removing unused ones. Also you will see there any that can be upgraded.

---

<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:** [25 September 2022 14:38 UTC](https://discourse.nodered.org/t/npm-install-issues/67561/10 "2022-09-25T14:38:02Z")

</div>

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