noflo / noflo-xpress

High-level Express.js components for NoFlo

noflo-xpress

High-level Express.js components for NoFlo

Installation

npm install --save noflo-xpress

Usage Examples

• Basic router
• Advanced router
• RESTful Resource

Changelog

0.6.0

• Migrated from CoffeeScript to modern JavaScript

0.5.0

• Updated for NoFlo 1.x

0.4.1

• fixed lifecycle for Server component

0.4.0

• added RESTful Resource router component

0.3.0

• using process api in components & test_components
• components/Router does not store state, components/Server saves server as scoped state for shutdown()
• using noflo 0.8
• only 1 router for everything, removed lib/
• bumped express, uuid, and mocha dependencies
• testing on 4.x and 6.x on Travis

0.2.2

• bumped chai, noflo, and mocha dependencies

0.2.1

• req.uuid and res.uuid are set by routers before applying filters, so request id is now available in filters as well as in downstream processes.

0.2.0

• Split Router into 4 components with different inports: Router, PathRouter, FilterRouter and ComboRouter. No meta ports configuration anymore as it is not supported by Flowhub.
• FILTER port of type function is now FILTERS of type array of function which allows chaining multiple filters.
• Remove obsolete Route component, use routers instead.
• Remove unused ROUTER outport from routers.

noflo-xpress's Issues

Filter data races between routers

If a Router with a filter is configured within application graph before routers without filters, the filter gets applied to all the consequent filters. Either they race for Express application instance, or Express routers aren't so isolated. Or it's both of these reasons.

Server should be a generator

Currently NoFlo thinks the network has finished after setup, even though the HTTP server is actually listening for requests.

Either the server or the router(s) should be generator that keeps the network alive until server stops.

An in-range update of noflo is breaking the build 🚨

Version 1.0.3 of noflo was just published.

Branch	Build failing 🚨
Dependency	noflo
Current Version	1.0.2
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

noflo is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

1.0.3

Added support for running arbitrary NoFlo graphs via noflo.asCallback. You can call this function now with either a component name, or a noflo.Graph instance

Commits

The new version differs by 6 commits.

• 955ecf4 Release 1.0.3
• 7f3b3b1 Document asCallback new features
• f3d951d Merge pull request #583 from noflo/ascallback_arbitrary
• 6dcad76 Allow running asCallback with a graph instance, fixes #582
• b0ebeb1 Unhardcode the assumption of single process and work with graph data
• 83d134a Tests for asCallback with a graph, refs #582

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of mocha is breaking the build 🚨

The devDependency mocha was updated from 6.0.2 to 6.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v6.1.0

6.1.0 / 2019-04-07

🔒 Security Fixes

• #3845: Update dependency "js-yaml" to v3.13.0 per npm security advisory (@plroebuck)

🎉 Enhancements

• #3766: Make reporter constructor support optional options parameter (@plroebuck)
• #3760: Add support for config files with .jsonc extension (@sstephant)

📠 Deprecations

These are soft-deprecated, and will emit a warning upon use. Support will be removed in (likely) the next major version of Mocha:

• #3719: Deprecate this.skip() for "after all" hooks (@juergba)

🐛 Fixes

• #3829: Use cwd-relative pathname to load config file (@plroebuck)
• #3745: Fix async calls of this.skip() in "before each" hooks (@juergba)
• #3669: Enable --allow-uncaught for uncaught exceptions thrown inside hooks (@givanse)

and some regressions:

• #3848: Fix Suite cloning by copying root property (@fatso83)
• #3816: Guard against undefined timeout option (@boneskull)
• #3814: Update "yargs" in order to avoid deprecation message (@boneskull)
• #3788: Fix support for multiple node flags (@aginzberg)

📖 Documentation

• mochajs/mocha-examples: New repository of working examples of common configurations using mocha (@craigtaub)
• #3850: Remove pound icon showing on header hover on docs (@jd2rogers2)
• #3812: Add autoprefixer to documentation page CSS (@Munter)
• #3811: Update doc examples "tests.html" (@DavidLi119)
• #3807: Mocha website HTML tweaks (@plroebuck)
• #3793: Update config file example ".mocharc.yml" (@cspotcode)

🔩 Other

• #3830: Replace dependency "findup-sync" with "find-up" for faster startup (@cspotcode)
• #3799: Update devDependencies to fix many npm vulnerabilities (@XhmikosR)

Commits

The new version differs by 28 commits.

• f4fc95a Release v6.1.0
• bd29dbd update CHANGELOG for v6.1.0 [ci skip]
• aaf2b72 Use cwd-relative pathname to load config file (#3829)
• b079d24 upgrade deps as per npm audit fix; closes #3854
• e87c689 Deprecate this.skip() for "after all" hooks (#3719)
• 81cfa90 Copy Suite property "root" when cloning; closes #3847 (#3848)
• 8aa2fc4 Fix issue 3714, hide pound icon showing on hover header on docs page (#3850)
• 586bf78 Update JS-YAML to address security issue (#3845)
• d1024a3 Update doc examples "tests.html" (#3811)
• 1d570e0 Delete "/docs/example/chai.js"
• ade8b90 runner.js: "self.test" undefined in Browser (#3835)
• 0098147 Replace findup-sync with find-up for faster startup (#3830)
• d5ba121 Remove "package" flag from sample config file because it can only be passes as CLI arg (#3793)
• a3089ad update package-lock
• 75430ec Upgrade yargs-parser dependency to avoid loading 2 copies of yargs

There are 28 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Use CoffeeScript.register() or require the coffeescript/register module to require .coffee files.

When I added this module to my noflo project, it crashes immediately on start (noflo-nodejs) with this error:

Use CoffeeScript.register() or require the coffeescript/register module to require .coffee files.

Didn't even use it, just added to dependencies.

Create a Resource router component

One common use case for making servers is exposing RESTful APIs, and so the easier we can make this the better.

The resource router could be somewhat inspired by https://www.npmjs.com/package/resourcemap and expose outports for the different REST operations on a resource.

Something like:

'/user' -> PATH UserResource(xpress/Resource)
UserResource LIST -> REQ ListUsers # GET /user
UserResource SHOW -> REQ ShowUser # GET /user/:name
UserResource UPDATE -> REQ UpdateUser # PUT /user/:name
UserResource DELETE -> REQ DeleteUser # DELETE /user/:name

non-connected outports should result in either 404 or 405 depending on the case

Server doesn't implement shutdown()

Just like with noflo-webserver the noflo-xpress Server should also close the server when receiving a shutdown() from the network coordinator.

Write req.uuid before applying filters

This would allow logger filters to log request id, for instance.