NoFlo Component Loader generator for WebPack and other module bundlers
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
example
lib
spec Support ES6 directly without babel, fixes #5 Jan 11, 2018
.eslintrc.json
.gitignore Release 0.3.1 Jul 28, 2018
.travis.yml
README.md
index.js
package.json Release 0.3.2 Sep 23, 2018

README.md

NoFlo Component Loader generator Build Status Greenkeeper badge

This utility can be used for generating statically configured NoFlo component loaders when building NoFlo with a module bundler like WebPack.

Usage

Install this library as a development dependency:

$ npm install noflo-component-loader --save-dev

Then configure WebPack to replace NoFlo's dynamic component loader with a generated one. Add to your module.rules:

{
  // Replace NoFlo's dynamic loader with a generated one
  test: /noflo\/lib\/loader\/register.js$/,
  use: [
    {
      loader: 'noflo-component-loader',
      options: {
        // Only include components used by this graph
        // Set to NULL if you want all installed components
        graph: 'myproject/GraphName',
        // Whether to include the original component sources
        // in the build
        debug: false,
      },
    },
  ],
},

Note: If you need to support building on Windows, the test above must be adapted to the \ path separator. Use ([\\]+|\/) instead of \/.

For a more complete example, see the example/ folder.

Changes

  • 0.3.2 (Sep 23 2018)
    • Fixed getSource handling of components without a library prefix
  • 0.3.1 (Jul 28 2018)
    • setSource failures now provide more verbose errors including the component library and name
  • 0.3.0 (Jan 11 2018)
    • Try to run ES6 components directly without transpiling if Babel is not available. Most platforms support it now