node-red/packages/node_modules/@node-red/registry
Nick O'Leary d2c9ccbfdd
Detect externalModule dependencies inside subflow modules
Not sure this is 100% the right approach. If a subflow module has a dependency
it should be in the subflow's package.json and therefore installed next to the
subflow module in ~/.node-red/node_modules.

By treating it as a 'normal' external module, it will be dynamically installed
in ~/.node-red/externalModules. That then exposes the module to the user
who won't know why its there and may remove it.

It would be better to allow nodes inside a subflow module to require
from ~/.node-red/node_modules and not limit it to the externalModules
dir. The hard part is knowing when to do that.
2021-02-14 00:02:08 +00:00
..
lib Detect externalModule dependencies inside subflow modules 2021-02-14 00:02:08 +00:00
.npmignore Add pack-modules grunt task 2018-10-25 11:18:13 +01:00
LICENSE Add LICENSE to each package 2018-08-21 13:57:59 +01:00
README.md Add README files to each package 2018-08-21 13:43:11 +01:00
package.json Merge branch 'master' into dev 2021-01-07 10:17:50 +00:00

README.md

@node-red/registry

Node-RED node registry module.

This provides the node registry, responsible for discovering and managing the node modules available to the Node-RED runtime.

Source

The main Node-RED modules are maintained as a monorepo on GitHub.