New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support scoped modules #885
Comments
A workaround we used for scoped modules was to have node-red embedded into an express app, then pass the "nodesDir" setting pointing to the installed node_modules/@scope folder, when doing RED.init(server,settings). All the nodes are then installed through the package.json of the express app. |
tried out 0.14.0 branch and get TypeError with installed scoped package - package works fine without scope in name of package.json - did I need some more to configure in the package.json? TypeError: Cannot read property 'nodes' of undefined |
Ah... you found a deficiency in my testing. Will take another look. |
With this commit 9e26aee the 0.14.0 branch should now properly handle scoped modules |
very well - Thank you! It works. |
Node-red doesn't appear to have the ability to pick up scoped modules installed to
$HOME/.node-red
which are installed with a parent directory named after the module scope (i.e.node_modules/@myscope/my-node
instead of justnode_modules/my-node
). Are there any workarounds for nodes that are published to private registries under a package scope? Would it be possible to modify the lookup code to peek inside any directories beginning with@
and include nodes found in there?The text was updated successfully, but these errors were encountered: