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
..
deprecated.js	Remove pi gpi, twitter, email and feedparser nodes from core	2019-05-17 14:08:51 +01:00
externalModules.js	Detect externalModule dependencies inside subflow modules	2021-02-14 00:02:08 +00:00
index.js	Merge branch 'dev' into function-modules	2021-02-13 00:21:27 +00:00
installer.js	Handle subflow modules with their own npm dependencies	2021-01-07 11:26:20 +00:00
library.js	Merge branch 'master' into dev	2021-01-27 23:28:19 +00:00
loader.js	Fix merge of dev	2021-01-26 13:44:38 +00:00
localfilesystem.js	Initial plugin runtime api implementation	2021-01-18 16:25:40 +00:00
plugins.js	Add initial support for ThemePlugins	2021-01-26 13:49:47 +00:00
registry.js	Detect externalModule dependencies inside subflow modules	2021-02-14 00:02:08 +00:00
subflow.js	Use subflow.info for help text and meta.type for node type	2021-01-07 15:34:27 +00:00
util.js	Merge branch 'dev' into function-modules	2021-02-13 00:21:27 +00:00