Go to file
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
.github Update build.yml 2021-01-07 10:09:49 +00:00
packages/node_modules Detect externalModule dependencies inside subflow modules 2021-02-14 00:02:08 +00:00
scripts Move mosca to ui-test-dependencies list 2020-11-02 21:32:20 +00:00
test Detect externalModule dependencies inside subflow modules 2021-02-14 00:02:08 +00:00
.gitattributes Prevent github from suppressing diffs 2018-09-24 22:02:18 +01:00
.gitignore Migrate to nyc instead of istanbul for code coverage 2020-10-19 21:10:34 +01:00
.jshintrc add allow es6 to .jshintrc 2017-06-23 21:49:35 +01:00
.nodemonignore Fix grunt dev monitoring of src 2018-09-28 16:21:49 +01:00
.travis.yml Disable nyc coverage reporting on older node versions 2020-12-07 11:46:14 +00:00
API.md Move exec and events components to util module 2020-12-07 11:49:01 +00:00
CHANGELOG.md Bump for 1.2.8 2021-02-02 13:11:33 +00:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md Replace node.js with Node.js 2019-08-06 19:27:46 +09:00
Gruntfile.js Add RED.plugins module to editor 2021-01-18 16:25:40 +00:00
jsdoc.json More api documentation updates 2019-01-28 14:40:42 +00:00
LICENSE Update top-level copyright statements 2020-09-29 20:28:15 +01:00
package.json Merge branch 'dev' into function-modules 2021-02-13 00:21:27 +00:00
README.md Update top-level copyright statements 2020-09-29 20:28:15 +01:00
SECURITY.md Update top-level copyright statements 2020-09-29 20:28:15 +01:00

Node-RED

http://nodered.org

Build Status Coverage Status

Low-code programming for event-driven applications.

Node-RED: Low-code programming for event-driven applications

Quick Start

Check out http://nodered.org/docs/getting-started/ for full instructions on getting started.

  1. sudo npm install -g --unsafe-perm node-red
  2. node-red
  3. Open http://localhost:1880

Getting Help

More documentation can be found here.

For further help, or general discussion, please use the Node-RED Forum or slack team.

Developers

If you want to run the latest code from git, here's how to get started:

  1. Clone the code:

     git clone https://github.com/node-red/node-red.git
     cd node-red
    
  2. Install the node-red dependencies

     npm install
    
  3. Build the code

     npm run build
    
  4. Run

     npm start
    

Contributing

Before raising a pull-request, please read our contributing guide.

This project adheres to the Contributor Covenant 1.4. By participating, you are expected to uphold this code. Please report unacceptable behavior to any of the project's core team at team@nodered.org.

Authors

Node-RED is a project of the OpenJS Foundation.

It was created by IBM Emerging Technology.

Copyright OpenJS Foundation and other contributors, https://openjsf.org under the Apache 2.0 license.