Integration to IoT, often require pulling together different APIs, online services and hardware devices in new and interesting ways. Time spent figuring out how to access a Serial port, or to complete an OAuth flow against Twitter is not time spent on creating the real value of a solution. We need tools that make it easier for developers at all levels to create applications and allow them to focus on what is important.
browser and allows you to create applications by drawing flows of events. Each node in a flow represents a well-defined piece of functionality, such as updating a value, making a database query or sending a tweet. The developer configures each node as required, focused on what it does, not how it does it. When the flow is deployed to the Node-RED runtime, each node becomes a running piece of code and messages start passing through the flow. “Flow-based programming for event-driven applications”
the top- level package.json. Each module has its own package.json that lists only its own production dependencies. At development time, npm install is only run at the top level.
module that can be used by test files to access files in the main src tree. No point publishing as a standalone module as it is inherently tied to the code layout of the repository.
to the build so travis catches it when we don’t Two remaining issues: 1. doesn’t check optionalDeps 2. doesn’t catch if we forget to add a brand new dependency
release was updated to build a tgz for each module. They can be tested and manually published to npm Really should write a script to do the publishing – ensuring the right tag is used if it’s a beta release.