# Installed custom node not recognized in Node-red 1.3.1

**URL:** <https://discourse.nodered.org/t/installed-custom-node-not-recognized-in-node-red-1-3-1/44020>\
**Category:** General\
**Created:** [12 April 2021 08:46 UTC](https://discourse.nodered.org/t/installed-custom-node-not-recognized-in-node-red-1-3-1/44020 "2021-04-12T08:46:55Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Laurent\_D](https://avatars.discourse-cdn.com/v4/letter/l/ed655f/32.png) [@Laurent\_D](https://discourse.nodered.org/u/Laurent_D)\
**Post date:** [12 April 2021 08:46 UTC](https://discourse.nodered.org/t/installed-custom-node-not-recognized-in-node-red-1-3-1/44020/1 "2021-04-12T08:46:55Z")

</div>

In my previous setup (node-red 1.2.x), I used to install custom nodes (provided by someone else) by unzipping the node files in C:\Users\MyName\node\_modules, and it was working fine 🙂  
Note: My machine is always offline, so I need to install these nodes in offline mode.  
Since I upgraded to node-red 1.3.1, these nodes generate an error:

```auto
C:\Users\MyName>node-red
9 Apr 11:15:14 - [info]
Welcome to Node-RED
===================
9 Apr 11:15:14 - [info] Node-RED version: v1.3.1
9 Apr 11:15:14 - [info] Node.js version: v10.20.1
9 Apr 11:15:14 - [info] Windows_NT 10.0.19041 x64 LE
9 Apr 11:15:16 - [info] Loading palette nodes
9 Apr 11:15:16 - [error] Failed to start server:
9 Apr 11:15:16 - [error] TypeError: Cannot read property 'node-red-augmentedoperator' of undefined
    at C:\Users\MyName\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\registry\lib\localfilesystem.js:200:35
    at Array.forEach (<anonymous>)
    at scanTreeForNodesModules (C:\Users\MyName\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\registry\lib\localfilesystem.js:194:17)
    at Object.getNodeFiles (C:\Users\MyName\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\registry\lib\localfilesystem.js:334:27)
    at load (C:\Users\MyName\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\registry\lib\loader.js:42:35)
    at process._tickCallback (internal/process/next_tick.js:68:7)

```

I have found a workaround: unzip the files somewhere and then call `npm install <path_to_node>`

But, why doesn't it work like before?

---

<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:** [12 April 2021 09:10 UTC](https://discourse.nodered.org/t/installed-custom-node-not-recognized-in-node-red-1-3-1/44020/2 "2021-04-12T09:10:31Z")

</div>

Where is your Node-RED user directory located? Is there a `package.json` file in that directory?

I _think_ that error will happen if there is no package.json existing in that directory, which could happen if you just unzip the module and then run node-red. Running the npm install will generate the package.json if it doesn't exist.

---

<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:** [12 April 2021 09:22 UTC](https://discourse.nodered.org/t/installed-custom-node-not-recognized-in-node-red-1-3-1/44020/3 "2021-04-12T09:22:29Z")

</div>

> [@knolleary](#):
>
> I _think_ that error will happen if there is no package.json existing in that directory, which could happen if you just unzip the module and then run node-red.

I've managed to recreate and this was the issue.

The workaround is either run npm install as you do, or if you unzip it, then run `npm init -y` in your Node-RED user directory (`~/.node-red`) in order to create a default package.json file.

I'll fix the underlying issue for 1.3.2

---

<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:** [12 April 2021 09:35 UTC](https://discourse.nodered.org/t/installed-custom-node-not-recognized-in-node-red-1-3-1/44020/4 "2021-04-12T09:35:50Z")

</div>

> [@knolleary](#):
>
> then run `npm init -y` in your Node-RED user directory ( `~/.node-red` ) in order to create a default package.json file.

Actually its a bit more than that - the package.json needs to exist _and_ have a `dependencies` section - something `npm init -y` won't give you.

---

<div class="post-metadata">

**Author:** ![Laurent\_D](https://avatars.discourse-cdn.com/v4/letter/l/ed655f/32.png) [@Laurent\_D](https://discourse.nodered.org/u/Laurent_D)\
**Post date:** [12 April 2021 09:46 UTC](https://discourse.nodered.org/t/installed-custom-node-not-recognized-in-node-red-1-3-1/44020/5 "2021-04-12T09:46:07Z")

</div>

Thanks for your feedback and waiting for 1.3.2 🙂

---

<div class="post-metadata">

**Author:** ![Laurent\_D](https://avatars.discourse-cdn.com/v4/letter/l/ed655f/32.png) [@Laurent\_D](https://discourse.nodered.org/u/Laurent_D)\
**Post date:** [14 April 2021 11:52 UTC](https://discourse.nodered.org/t/installed-custom-node-not-recognized-in-node-red-1-3-1/44020/6 "2021-04-14T11:52:54Z")

</div>

I confirm that the issue is fixed in 1.3.2  
Thanks a lot and congratulation for your reactivity

---

<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:** [13 June 2021 11:53 UTC](https://discourse.nodered.org/t/installed-custom-node-not-recognized-in-node-red-1-3-1/44020/7 "2021-06-13T11:53:43Z")

</div>

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