Code Monkey home page Code Monkey logo

noflo-browser's Introduction

NoFlo: Flow-based programming for JavaScript

NoFlo is an implementation of flow-based programming for JavaScript running on both Node.js and the browser. From WikiPedia:

In computer science, flow-based programming (FBP) is a programming paradigm that defines applications as networks of "black box" processes, which exchange data across predefined connections by message passing, where the connections are specified externally to the processes. These black box processes can be reconnected endlessly to form different applications without having to be changed internally. FBP is thus naturally component-oriented.

Developers used to the Unix philosophy should be immediately familiar with FBP:

This is the Unix philosophy: Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface.

It also fits well in Alan Kay's original idea of object-oriented programming:

I thought of objects being like biological cells and/or individual computers on a network, only able to communicate with messages (so messaging came at the very beginning -- it took a while to see how to do messaging in a programming language efficiently enough to be useful).

NoFlo components can be written in any language that transpiles down to JavaScript, including ES6. The system is heavily inspired by J. Paul Morrison's book Flow-Based Programming.

Read more at https://noflojs.org/.

Suitability

NoFlo is not a web framework or a UI toolkit. It is a way to coordinate and reorganize data flow in any JavaScript application. As such, it can be used for whatever purpose JavaScript can be used for. We know of NoFlo being used for anything from building web servers and build tools, to coordinating events inside GUI applications, driving robots, or building Internet-connected art installations.

Tools and ecosystem

NoFlo itself is just a library for implementing flow-based programs in JavaScript. There is an ecosystem of tools around NoFlo and the fbp protocol that make it more powerful. Here are some of them:

  • Flowhub -- browser-based visual programming IDE for NoFlo and other flow-based systems
  • noflo-nodejs -- command-line interface for running NoFlo programs on Node.js
  • noflo-browser-app -- template for building NoFlo programs for the web
  • noflo-assembly -- industrial approach for designing NoFlo programs
  • fbp-spec -- data-driven tests for NoFlo and other FBP environments
  • flowtrace -- tool for retroactive debugging of NoFlo programs. Supports visual replay with Flowhub

See also the list of reusable NoFlo modules on NPM.

Requirements and installing

NoFlo is available for Node.js via NPM, so you can install it with:

$ npm install noflo --save

You can make a browser build of NoFlo using webpack. For webpack builds, you need configure the component loader statically with noflo-component-loader. For projects using Grunt, grunt-noflo-browser plugin makes this easy.

Installing from Git

NoFlo requires a reasonably recent version of Node.js, and some npm packages. Ensure that you have NoFlo checked out from Git, and all NPM dependencies installed. Build NoFlo with:

$ npm run build

Then you can install everything needed by a simple:

$ npm link

NoFlo is available from GitHub under the MIT license.

Changes

Please refer to the Release Notes and the CHANGES.md document.

Usage

Please refer to http://noflojs.org/documentation/. For visual programming with NoFlo, see https://docs.flowhub.io/.

Development

NoFlo development happens on GitHub. Just fork the main repository, make modifications and send a pull request.

We have an extensive suite of tests available for NoFlo. Run them with:

$ npm run build
$ npm test

Platform-specific tests

By default, the tests are run for both Node.js and the browser. You can also run only the tests for a particular target platform:

$ npm run test:node

or:

$ npm run test:browser

Discussion

There is a #noflo channel on the Flow-Based Programming Slack, and questions can be posted with the noflo tag on Stack Overflow. See http://noflojs.org/support/ for other ways to get in touch.

noflo-browser's People

Contributors

bergie avatar dependabot[bot] avatar greenkeeper[bot] avatar jonnor avatar jpka avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

noflo-browser's Issues

WebRTC support fails to load over HTTPS

Mixed Content: The page at 'https://noflojs.org/noflo-browser/everything.html?fbp_noload=true&fbp_protocol=iframe' was loaded over HTTPS, but requested an insecure script 'http://cdn.rawgit.com/rtc-io/rtc/v3.1.1/dist/rtc.js'. This request has been blocked; the content must be served over HTTPS.

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

Version 1.2.0 of grunt-noflo-browser just got published.

Branch Build failing 🚨
Dependency grunt-noflo-browser
Current Version 1.1.5
Type devDependency

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

As grunt-noflo-browser is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


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

The new version differs by 9 commits .

  • 52d9a02 Bump
  • 87d8de9 Merge pull request #17 from noflo/webpack2
  • 07d7e7b Switch to the new module rules option
  • d3017c3 Update webpack2
  • 7fa70ba fix(package): update webpack to version 2.2.1
  • 2e7b87a chore(package): update fbp-manifest to version 0.1.13
  • 855eb9f Drop the empty extension
  • fda4f84 json-loader is no longer needed
  • 2aef731 Bump to webpack2

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

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

The devDependency webpack was updated from 4.35.0 to 4.35.1.

🚨 View failing branch.

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

webpack 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 could not complete due to an error (Details).

Release Notes for v4.35.1

Bugfixes

  • add realResource condition in rule to schema
  • fixes order of loaders when using a matchResource
Commits

The new version differs by 20 commits.

  • 569dd6a 4.35.1
  • 5c7996d Merge pull request #9328 from jchapman127/bugfix/match-resource
  • fec4d53 only affect loader order when match resource is used
  • 61d508e improve test cases for more edge cases
  • 5523a0a Merge pull request #9326 from vankop/add-real-resource-parameter
  • 49dc747 fix loader ordering
  • a435c74 add test case for #9053
  • 68f794d updated snapshots, rerun tooling scripts
  • b320269 add realResource parameter to RuleSetRule
  • c8f4dd1 Merge pull request #9322 from webpack/dependabot/npm_and_yarn/@types/node-10.14.10
  • 498834c Merge pull request #9321 from webpack/dependabot/npm_and_yarn/eslint-plugin-jest-22.7.1
  • 81bf2ca chore(deps-dev): bump @types/node from 10.14.9 to 10.14.10
  • f8bb7a5 chore(deps-dev): bump eslint-plugin-jest from 22.7.0 to 22.7.1
  • 58bd580 Merge pull request #9311 from webpack/dependabot/npm_and_yarn/eslint-plugin-jest-22.7.0
  • cea1348 Merge pull request #9310 from ryandrew14/update-contributing-to-documentation

There are 20 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 🌴

Don't depend on grunt-noflo-browser

Should be other way around, that one should depend on this repo.
Will make it possible to use the noflo browser build stuff without Grunt, and to avoid having all the setup logic inside an HTML template...
And have tests for the stuff..

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

Version 1.1.0 of noflo was just published.

Branch Build failing 🚨
Dependency noflo
Current Version 1.0.3
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

Commits

The new version differs by 51 commits.

  • 145c9f3 Release 1.1.0
  • 39a2dbf Merge pull request #591 from noflo/introspection
  • acaee45 Document ES5 limitation with default values
  • a9334d7 Provide example for wrapping built-in functions
  • bed1933 Explain why we skip
  • c8f357f Usage example in JavaScript
  • ff2adab Skip default value test in browser
  • f8fde39 Basic interface documentation
  • b2d6a5b Add support for params with default values
  • 3775783 Only attach ports that have input going to them to make defaults work
  • cd89107 Set up bracket forwarding
  • 80ae859 Test with a native function
  • 6cbd4f5 Add support for zero-parameter functions
  • 5a1111c Add support for Node.js style async functions
  • 2f1697c Move skip one level down

There are 51 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 🌴

Add versioned deploy

Currently we deploy only to noflojs.org/noflo-browser/$target. Should also have a noflojs.org/noflo-browser/$maj.$min.$patch/$target (for refering to specific version), and possibly a noflojs.org/noflo-browser/$major/$target (following semver, for ensuring no breaking changes).

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

The devDependency puppeteer was updated from 1.18.0 to 1.18.1.

🚨 View failing branch.

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

puppeteer 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 could not complete due to an error (Details).

Release Notes for v1.18.1

Big Changes

  • Chromium 77.0.3835.0 (r672088)

API changes

No API changes.

Bug Fixes

  • #4610 - What's going on with Chromium size, it has grown three times in the latest minor release (1.17.0 -> 1.18.0)

Raw notes

d07c70a - chore: mark version v1.18.1
cf34583 - feat(chromium): roll Chromium to r672088 (#4626)
411347c - chore: bump version to v1.18.0-post (#4608)

Commits

The new version differs by 3 commits.

  • a2cf81d chore: mark version v1.18.1 (#4628)
  • cf34583 feat(chromium): roll Chromium to r672088 (#4626)
  • 411347c chore: bump version to v1.18.0-post (#4608)

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 babel-loader is breaking the build 🚨


☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The devDependency babel-loader was updated from 8.0.6 to 8.1.0.

🚨 View failing branch.

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

babel-loader 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 could not complete due to an error (Details).

Release Notes for 8.1.0
Commits

The new version differs by 18 commits.

  • 3ff9926 8.1.0
  • 0817bb6 Bump deps for audit (#834)
  • ecb2b02 Bump acorn from 6.3.0 to 6.4.1 (#828)
  • 13a8238 feat: expose webpack target via babel caller (#826)
  • b568420 Merge pull request #814 from nicolo-ribaudo/tla
  • 1c35731 Update src/injectCaller.js
  • 5f55638 Add schema validation (#822)
  • 8b47312 Merge pull request #821 from PatNeedham/docs/contributing-typo
  • a967311 docs(contributing): fix typo
  • 758d4b5 docs(readme): fix typo (#818)
  • 8a0a25a Add supportsTopLevelAwait to caller
  • 15df92f chore: Do not run node 6 in appveyor
  • 26d1676 chore: Upgrade more dev dependencies
  • 26aa687 chore: Update some dev dependencies
  • a961168 Bump eslint-utils from 1.3.1 to 1.4.2 (#806)

There are 18 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 🌴

An in-range update of simple-server is breaking the build 🚨

Version 1.1.0 of simple-server was just published.

Branch Build failing 🚨
Dependency simple-server
Current Version 1.0.1
Type devDependency

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

simple-server 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

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 🌴

Port to WebPack

Nowadays we're using NPM for module installs also with browser, and webpack for building.

grunt-noflo-browser has to functionality needed for these builds.

However, there are two blockers:

  • grunt-noflo-browser component loader doesn't support live programming features:
  • some of our dependencies are not yet available on NPM. Missing:
    • noflo-runtime-iframe
    • noflo-draggabilly (d4)
    • noflo-gum (forrest)
    • noflo-seriously (forrest)
    • noflo-prompts (alfa256)
    • noflo-clmtrackr (forrest)
    • noflo-webaudio
    • noflo-tween

grunt build failed: can't find remote for "jashkenas/underscore"

Related to noflo/noflo#355

Running "build" task

Running "bower-install-simple:deps" (bower-install-simple) task
Executing Bower (Command: install)

Running "noflo_manifest:update" (noflo_manifest) task
File "component.json" updated.
File "package.json" updated.

Running "noflo_browser:everything" (noflo_browser) task
install noflo/noflo@master
install noflo/noflo-runtime-iframe@master
install noflo/noflo-runtime-webrtc@master
install noflo/noflo-runtime@master
install noflo/noflo-ajax@master
install noflo/noflo-core@master
install noflo/noflo-css@master
install noflo/noflo-dom@master
install noflo/noflo-flow@master
install noflo/noflo-groups@master
install noflo/noflo-interaction@master
install noflo/noflo-localstorage@master
install noflo/noflo-math@master
install noflo/noflo-objects@master
install noflo/noflo-packets@master
install noflo/noflo-physics@master
install noflo/noflo-routers@master
install noflo/noflo-strings@master
install noflo/noflo-websocket@master
install noflo/noflo-indexeddb@master
install noflo/noflo-github@master
install noflo/noflo-finitedomain@master
install d4tocchini/noflo-draggabilly@master
install forresto/noflo-gum@master
install forresto/noflo-seriously@master
install jonnor/noflo-cad@master
install jonnor/noflo-3dprint@master
install alfa256/noflo-prompts@master
install noflo/noflo-image@master
install noflo/noflo-ccv@master
install noflo/noflo-canvas@master
install automata/noflo-geometry@master
install forresto/noflo-clmtrackr@master
install automata/noflo-webaudio@master
install noflo/noflo-tween@master
install noflo/noflo-adapters@master
install noflo/noflo-amd@master
install noflo/noflo-react@master
install noflo/noflo-peer@master
install visionmedia/[email protected]
Fatal error: can't find remote for "jashkenas/underscore"

My guess is that not all of the component library dependencies for noflo-browser have been updated.

An in-range update of coffee-script is breaking the build 🚨

Version 1.12.8 of coffee-script was just published.

Branch Build failing 🚨
Dependency coffee-script
Current Version 1.12.7
Type devDependency

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

coffee-script 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

Commits

The new version differs by 11 commits ahead by 11, behind by 7.

  • 943579a 1.12.8 (#4801)
  • 8bb89d8 Backport #4783, fix for export default followed by an implicit object (#4800)
  • f301b04 [CS1] Add postinstall message for direct installs of ‘coffee-script’ (#4759)
  • c5f4314 [CS1] Travis CI for 1.x (#4797)
  • 1ad9c61 Revise v1 docs to reflect that v2 is out; update paths to reflect that the v2 docs are now the primary docs, and the v1 docs only live under /v1/
  • 249cc59 Remove v2 docs
  • e7073bc Update CS2 docs per #4688
  • 458440e 2.0.0-beta5 docs
  • 6cea181 [CS1] fix #4260 and #1349: splat error with soak properties or expressions (#4643)
  • e3c2c03 2.0.0-beta4 docs
  • 27f21a3 1.12.7 (#4617)

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 🌴

Avoid needing native Node.js modules when building for browser

The NPM packages for

Split out of #9

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

Version 1.0.2 of grunt was just published.

Branch Build failing 🚨
Dependency grunt
Current Version 1.0.1
Type devDependency

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

grunt 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

Commits

The new version differs by 27 commits.

  • ccc3163 v1.0.2
  • e7795dc Remove iojs from test matrix (#1622)
  • a6a133b Remove deprecation warning for coffeescript (#1621) r=@vladikoff
  • 06b377e https links to webchat.freenode.net and gruntjs.com (#1610)
  • 7c5242f Use node executable for local grunt bin for Windows support
  • f6cbb63 Oh right, Windows isnt bash
  • a9a20da Try and debug why appveyor is failing on npm
  • 48bba6c Move to the test script to avoid npm was unexpected at this time.
  • 6b97ac0 Try to fix appveyor script
  • 19003ba For appveyor, check node version to decide whether to install npm@3
  • 3fcf921 Install npm@3 if npm version is npm 1 or 2
  • 77fc157 Use the local version of grunt to run tests
  • 400601a Updating devDependencies
  • 6592ad1 Update travis/appveyor to node versions we support
  • b63aeec Dont manually install npm, use the version each node version corresponds with

There are 27 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 🌴

An in-range update of copy-webpack-plugin is breaking the build 🚨

The devDependency copy-webpack-plugin was updated from 5.0.3 to 5.0.4.

🚨 View failing branch.

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

copy-webpack-plugin 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 could not complete due to an error (Details).

Release Notes for v5.0.4

5.0.4 (2019-07-26)

Bug Fixes

  • use posix separator for emitting assets (#392) (7f08be6)
Commits

The new version differs by 9 commits.

  • 6158483 chore(release): 5.0.4
  • cd0e9f5 docs: clarify plugin description (#395)
  • f848140 test: refactor (#394)
  • ff0c736 refactor: tests (#393)
  • 7f08be6 fix: use posix separator for emitting assets (#392)
  • 89c73c8 chore(defaults): update (#390)
  • 0b61c86 docs: fix 'defined' typo in readme (#384)
  • 2f4dfec docs: update wording in README (#386)
  • 4b5a6bf chore(defaults): update (#380)

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 grunt-noflo-browser is breaking the build 🚨

Version 1.4.0 of grunt-noflo-browser was just published.

Branch Build failing 🚨
Dependency grunt-noflo-browser
Current Version 1.3.2
Type devDependency

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

grunt-noflo-browser 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

Commits

The new version differs by 8 commits.

  • 49cbe83 Bump
  • f6ac38e Merge pull request #30 from noflo/noflo_component_loader
  • 9935b00 Try to match also Windows paths with regexp
  • c188098 Bump noflo-component-loader dep
  • 84cec54 Update to legacy-free component versions
  • 821de79 Test on modern Node.js
  • ea16584 Use noflo-component-loader to build the loader
  • f00089b Remove obsolete grunt-noflo-manifest

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 webpack is breaking the build 🚨

Version 3.11.0 of webpack was just published.

Branch Build failing 🚨
Dependency webpack
Current Version 3.10.0
Type devDependency

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

webpack 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

Commits

The new version differs by 62 commits.

  • f010546 update examples
  • bc840ec 3.11.0
  • 9323ee6 Merge pull request #6398 from addaleax/no-binding
  • c7cbc35 Merge pull request #6430 from jbottigliero/update/ajv
  • 61b75b7 update ajv + ajv-keywords
  • 8da8b93 Work around Node environment variable bug
  • ddb1fad Merge pull request #6408 from ocombe/fix/#6407-empty-array
  • 2aebfbe fix(ConcatenatedModule): don't throw on arrays with empty values
  • 3972d9a Merge pull request #6391 from nerdkid93/patch-1
  • e4375f8 Avoid relying on Node’s internals
  • 0dd1727 change polymer loader link
  • 33f518b Merge pull request #6300 from nename0/fix-6243
  • 80ed1c4 Merge pull request #6335 from Connormiha/banner-plugin-optimize
  • 5d93c53 Minor optimize banner plugin
  • 1895b76 Add Tests checking chunkhash of runtime chunk only changes if needed

There are 62 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 🌴

Not working

Progress: resolved 933, reused 823, downloaded 108, added 966, done
node_modules/.pnpm/[email protected][email protected]/node_modules/noflo-react: Running postinstall script, failed in 15ms
.../node_modules/noflo-react postinstall$ ./node_mod
│ '.' �����ڲ����ⲿ���Ҳ���ǿ����еij���
│ ���������ļ���
└─ Failed in 15ms at E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\noflo-react
 ELIFECYCLE  Command failed with exit code 1.

After remove noflo-react

> [email protected] build E:\repo\noflo-browser
> webpack

[webpack-cli] Error: Cannot find module 'workbox-build/build/options/schema/webpack-generate-sw'
Require stack:
- E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\workbox-webpack-plugin\build\generate-sw.js
- E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\workbox-webpack-plugin\build\index.js
- E:\repo\noflo-browser\webpack.config.js
- E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\webpack-cli\lib\groups\resolveConfig.js
- E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\webpack-cli\lib\webpack-cli.js
- E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\webpack-cli\lib\bootstrap.js
- E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\webpack-cli\bin\cli.js
- E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\webpack\bin\webpack.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1070:15)
    at Module._load (node:internal/modules/cjs/loader:923:27)
    at Module.require (node:internal/modules/cjs/loader:1137:19)
    at require (E:\repo\noflo-browser\node_modules\.pnpm\[email protected]\node_modules\v8-compile-cache\v8-compile-cache.js:159:20)
    at Object.<anonymous> (E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\workbox-webpack-plugin\build\generate-sw.js:20:33)
    at Module._compile (E:\repo\noflo-browser\node_modules\.pnpm\[email protected]\node_modules\v8-compile-cache\v8-compile-cache.js:192:30)
    at Module._extensions..js (node:internal/modules/cjs/loader:1309:10)
    at Module.load (node:internal/modules/cjs/loader:1113:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)
    at Module.require (node:internal/modules/cjs/loader:1137:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    'E:\\repo\\noflo-browser\\node_modules\\.pnpm\\[email protected][email protected]\\node_modules\\workbox-webpack-plugin\\build\\generate-sw.js',
    'E:\\repo\\noflo-browser\\node_modules\\.pnpm\\[email protected][email protected]\\node_modules\\workbox-webpack-plugin\\build\\index.js',
    'E:\\repo\\noflo-browser\\webpack.config.js',
    'E:\\repo\\noflo-browser\\node_modules\\.pnpm\\[email protected][email protected]\\node_modules\\webpack-cli\\lib\\groups\\resolveConfig.js',
    'E:\\repo\\noflo-browser\\node_modules\\.pnpm\\[email protected][email protected]\\node_modules\\webpack-cli\\lib\\webpack-cli.js',
    'E:\\repo\\noflo-browser\\node_modules\\.pnpm\\[email protected][email protected]\\node_modules\\webpack-cli\\lib\\bootstrap.js',
    'E:\\repo\\noflo-browser\\node_modules\\.pnpm\\[email protected][email protected]\\node_modules\\webpack-cli\\bin\\cli.js',
    'E:\\repo\\noflo-browser\\node_modules\\.pnpm\\[email protected][email protected]\\node_modules\\webpack\\bin\\webpack.js'
  ]
}
 ELIFECYCLE  Command failed with exit code 2.

 *  终端进程“C:\Program Files\PowerShell\7\pwsh.exe -Command pnpm run build”已终止,退出代码: 1。 
 *  终端将被任务重用,按任意键关闭。 

 *  正在执行任务: pnpm run build 


> [email protected] build E:\repo\noflo-browser
> webpack

[webpack-cli] Error: Cannot find module 'workbox-build/build/options/schema/webpack-generate-sw'
Require stack:
- E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\workbox-webpack-plugin\build\generate-sw.js
- E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\workbox-webpack-plugin\build\index.js
- E:\repo\noflo-browser\webpack.config.js
- E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\webpack-cli\lib\groups\resolveConfig.js
- E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\webpack-cli\lib\webpack-cli.js
- E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\webpack-cli\lib\bootstrap.js
- E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\webpack-cli\bin\cli.js
- E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\webpack\bin\webpack.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1070:15)
    at Module._load (node:internal/modules/cjs/loader:923:27)
    at Module.require (node:internal/modules/cjs/loader:1137:19)
    at require (E:\repo\noflo-browser\node_modules\.pnpm\[email protected]\node_modules\v8-compile-cache\v8-compile-cache.js:159:20)
    at Object.<anonymous> (E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\workbox-webpack-plugin\build\generate-sw.js:20:33)
    at Module._compile (E:\repo\noflo-browser\node_modules\.pnpm\[email protected]\node_modules\v8-compile-cache\v8-compile-cache.js:192:30)
    at Module._extensions..js (node:internal/modules/cjs/loader:1309:10)
    at Module.load (node:internal/modules/cjs/loader:1113:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)
    at Module.require (node:internal/modules/cjs/loader:1137:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    'E:\\repo\\noflo-browser\\node_modules\\.pnpm\\[email protected][email protected]\\node_modules\\workbox-webpack-plugin\\build\\generate-sw.js',
    'E:\\repo\\noflo-browser\\node_modules\\.pnpm\\[email protected][email protected]\\node_modules\\workbox-webpack-plugin\\build\\index.js',
    'E:\\repo\\noflo-browser\\webpack.config.js',
    'E:\\repo\\noflo-browser\\node_modules\\.pnpm\\[email protected][email protected]\\node_modules\\webpack-cli\\lib\\groups\\resolveConfig.js',
    'E:\\repo\\noflo-browser\\node_modules\\.pnpm\\[email protected][email protected]\\node_modules\\webpack-cli\\lib\\webpack-cli.js',
    'E:\\repo\\noflo-browser\\node_modules\\.pnpm\\[email protected][email protected]\\node_modules\\webpack-cli\\lib\\bootstrap.js',
    'E:\\repo\\noflo-browser\\node_modules\\.pnpm\\[email protected][email protected]\\node_modules\\webpack-cli\\bin\\cli.js',
    'E:\\repo\\noflo-browser\\node_modules\\.pnpm\\[email protected][email protected]\\node_modules\\webpack\\bin\\webpack.js'
  ]
}
 ELIFECYCLE  Command failed with exit code 2.

 *  终端进程“C:\Program Files\PowerShell\7\pwsh.exe -Command pnpm run build”已终止,退出代码: 1。 
 *  终端将被任务重用,按任意键关闭。 

After comment out // const { GenerateSW: GenerateServiceWorker } = require('workbox-webpack-plugin');

 *  正在执行任务: pnpm run build 


> [email protected] build E:\repo\noflo-browser
> webpack

node:internal/crypto/hash:69
  this[kHandle] = new _Hash(algorithm, xofLen);
                  ^

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:69:19)
    at Object.createHash (node:crypto:138:10)
    at BulkUpdateDecorator.hashFactory (E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\webpack\lib\util\createHash.js:138:18)
    at BulkUpdateDecorator.update (E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\webpack\lib\util\createHash.js:44:50)
    at OriginalSource.updateHash (E:\repo\noflo-browser\node_modules\.pnpm\[email protected]\node_modules\webpack-sources\lib\OriginalSource.js:104:8)
    at NormalModule._initBuildHash (E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\webpack\lib\NormalModule.js:736:17)
    at handleParseResult (E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\webpack\lib\NormalModule.js:800:10)
    at E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\webpack\lib\NormalModule.js:853:4
    at processResult (E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\webpack\lib\NormalModule.js:624:11)
    at E:\repo\noflo-browser\node_modules\.pnpm\[email protected][email protected]\node_modules\webpack\lib\NormalModule.js:675:5 {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v20.2.0
 ELIFECYCLE  Command failed with exit code 1.

 *  终端进程“C:\Program Files\PowerShell\7\pwsh.exe -Command pnpm run build”已终止,退出代码: 1。 
 *  终端将被任务重用,按任意键关闭。 

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

Version 2.2.0 of coffeescript was just published.

Branch Build failing 🚨
Dependency coffeescript
Current Version 2.1.1
Type devDependency

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

coffeescript 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

Commits

The new version differs by 22 commits.

  • 0490eb9 2.2.0 (#4873)
  • 9e80f6f Fix #2047: Infinite loop possible when for loop with range uses variables (#4853)
  • fc5ab1a Update output
  • 0aa77f1 fix #4871 (#4872)
  • 1849f0d Fix #4852, @get @set implicit object (#4867)
  • d86597d Fix #3306: trailing comma in a function call in the last line throws a syntax error (#4860)
  • bf91781 Fix #4868: Incorrect ‘Can’t call super with @params’ error (#4869)
  • dcd6de9 Update output
  • 70b510b Fix #3933: Missing then doesn’t trigger nearby error (#4862)
  • 84d596d Fix #4437: variable scope in chained calls (#4863)
  • c804087 Fix #3921 & #2342: inline function without parentheses used in condition, inline 'else' (#4838)
  • 74bd537 fix #3909 (#4861)
  • 0217ed5 Fix #1726: expression in property access causes unexpected results (#4851)
  • e53307b Fix #3441: parentheses wrapping expression throw invalid error (#4849)
  • c8c8c16 Fix #4843: bad output when assigning to @prop in destructuring assignment with defaults (#4848)

There are 22 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 🌴

Add a minimal build target

Would go up on noflojs.org/noflo-browser next to everything.js/html

Could be used for quick&easy deployment scenarios. Would need to make sure that there is a way to inject custom component libraries without doing a rebuild though.

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


☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The devDependency grunt was updated from 1.0.4 to 1.1.0.

🚨 View failing branch.

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

grunt 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 could not complete due to an error (Details).

Release Notes for v1.1.0
  • Update to mkdirp ~1.0.3
  • Only support versions of Node >= 8
Commits

The new version differs by 8 commits.

  • d5cdac0 Merge pull request #1706 from gruntjs/tag-neew
  • 4674c59 v1.1.0
  • 6124409 Merge pull request #1705 from gruntjs/mkdirp-update
  • 0a66968 Fix up Buffer usage
  • 4bfa98e Support versions of node >= 8
  • f1898eb Update to mkdirp ~1.0.3
  • 75da17b HTTPS link to gruntjs.com (#1683)
  • 6795d31 Update js-yaml dependecy to ~3.13.1 (#1680)

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.1.4 to 6.2.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 could not complete due to an error (Details).

Release Notes for v6.2.0

6.2.0 / 2019-07-18

🎉 Enhancements

🐛 Fixes

📖 Documentation

🔍 Coverage

🔩 Other

Commits

The new version differs by 39 commits.

  • bd47776 Release v6.2.0
  • cc595af update CHANGELOG.md for v6.2.0 [ci skip]
  • 59d70ee fix: remove duplicate line-height property (#3957)
  • f77cac4 fix: do not redeclare variable (#3956)
  • 6201e42 Hide stacktrace when cli args are missing (#3963)
  • 88f45d5 Don't re-initialize grep option on watch re-run (#3960)
  • 5d4dd98 Fix No Files error when file is passed via --files (#3942)
  • 15b96af Collect test files later (#3953)
  • ccee5f1 Base reporter store ref to console.log (#3725)
  • 47318a7 update @mocha/contributors to v1.0.4 (#3944)
  • c903147 More, improved integration tests for watching (#3929)
  • e341ea4 Update CI config files to use Node-12.x (#3919)
  • 3064d25 update @mocha/docdash to v2.1.1 (#3945)
  • 9ea45e7 do not fork if no node flags present (#3827)
  • d02a096 modify Mocha constructor to accept options.global or options.globals (#3914)

There are 39 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 🌴

An in-range update of uglifyjs-webpack-plugin is breaking the build 🚨

Version 1.1.7 of uglifyjs-webpack-plugin was just published.

Branch Build failing 🚨
Dependency uglifyjs-webpack-plugin
Current Version 1.1.6
Type devDependency

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

uglifyjs-webpack-plugin 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 could not complete due to an error Details

Commits

The new version differs by 4 commits.

  • 75943e1 chore(release): 1.1.7
  • 2343274 fix(index): reduce memory consumption (cacheKey.hash) (#215)
  • 7d1b487 test: update snapshots (#214)
  • f66f6f0 docs(README): mangle.props instead of mangle.properties (#207)

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 grunt-noflo-browser is breaking the build 🚨

Version 1.3.0 of grunt-noflo-browser just got published.

Branch Build failing 🚨
Dependency grunt-noflo-browser
Current Version 1.2.0
Type devDependency

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

As grunt-noflo-browser is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

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

Commits

The new version differs by 14 commits.

  • d01f8b1 Update docs, refs #25
  • a7653fd Bump
  • 83d9573 Merge pull request #25 from noflo/opener_protocol
  • 8a8f257 Fix indent
  • cd150ba Provide runtime type correctly
  • 31acbd7 No need to log the debug URL, since we need to go through the button
  • 6321a65 Switch from iframe+webrtc to postmessage runtime
  • b694bb7 README: Minor doc improvements
  • 24f2afa Merge pull request #24 from noflo/greenkeeper/webpack-3.0.0
  • e8c9cce fix(package): update webpack to version 3.0.0
  • 83a6b19 Merge pull request #23 from noflo/greenkeeper/chai-4.0.0
  • d3e2bcf chore(package): update chai to version 4.0.0
  • 361e0ed Update tests for 0.8
  • 1e6ca6e Abort on parse errors

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

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

There have been updates to the babel7 monorepo:

    • The devDependency @babel/core was updated from 7.4.5 to 7.5.0.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 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 could not complete due to an error (Details).

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 karma is breaking the build 🚨

The devDependency karma was updated from 3.1.1 to 3.1.2.

🚨 View failing branch.

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

karma 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 v3.1.2

Bug Fixes

Features

Commits

The new version differs by 11 commits.

  • 7d4d347 chore: release v3.1.2
  • 5077c18 chore: update contributors
  • fb05fb1 fix(server): use flatted for json.stringify (#3220)
  • 2682bff feat(docs): callout the key debug strategies. (#3219)
  • 4e87902 fix(changelog): remove release which does not exist (#3214)
  • 30ff73b fix(browser): report errors to console during singleRun=false (#3209)
  • 5334d1a fix(file-list): do not preprocess up-to-date files (#3196)
  • dc5f5de fix(deps): upgrade sinon-chai 2.x -> 3.x (#3207)
  • d38f344 fix(package): bump lodash version (#3203)
  • ffb41f9 refactor(browser): log state transitions in debug (#3202)
  • 240209f fix(dep): Bump useragent to fix HeadlessChrome version (#3201)

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 karma is breaking the build 🚨

The devDependency karma was updated from 4.1.0 to 4.2.0.

🚨 View failing branch.

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

karma 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 could not complete due to an error (Details).

Release Notes for v4.2.0

Bug Fixes

  • logging: Util inspect for logging the config. (#3332) (70b72a9)
  • reporter: format stack with 1-based column (#3325) (182c04d), closes #3324
  • server: Add error handler for webserver socket. (#3300) (fe9a1dd)
Commits

The new version differs by 13 commits.

  • 42933c9 chore: release v4.2.0
  • db1ea57 chore: update contributors
  • a1049c6 chore: update eslint packages to latest and fix complaints (#3312)
  • 70b72a9 fix(logging): Util inspect for logging the config. (#3332)
  • 1087926 fix typo: (#3334)
  • 182c04d fix(reporter): format stack with 1-based column (#3325)
  • f0c4677 docs(travis): Correct the docs to also show how to do it on Xenial (#3316)
  • 3aea7ec chore(deps): update core-js -> ^3.1.3 (#3321)
  • 5e11340 chore: revert back to Mocha 4 (#3313)
  • 1205bce chore(test): fix flaky test cases (#3314)
  • 7f40349 Cleanup dependencies (#3309)
  • 7828bea chore: update braces and chokidar to latest versions (#3307)
  • fe9a1dd fix(server): Add error handler for webserver socket. (#3300)

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 coffeescript is breaking the build 🚨

The devDependency coffeescript was updated from 2.4.1 to 2.5.0.

🚨 View failing branch.

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

coffeescript 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 could not complete due to an error (Details).

Commits

The new version differs by 136 commits.

  • 61d408f 2.5.0 (#5284)
  • ba41b44 Allow linebreak/indent in destructured for variable (#5286)
  • 33bbef9 Merge pull request #5285 from helixbass/browser-compiler-call-parsing-error
  • c4f0c9e don't return boolean from grammar rule
  • 8677a0d Update output from #5275
  • ee2a107 AST: Refactor marking nodes that return (#5275)
  • 8fb5c1b Make it clearer that we're adding a property to an object
  • b2b2f97 Fix comments after colons getting lost (#5276)
  • 0045cb2 Colons are apparently another token type that doesn't survive passing through the parser, so rescue any comments attached to colons
  • a8273bf No need for separate ast returns method, as it's never overridden
  • 3e7c570 AST (#5273)
  • a34c0c9 Return Root from nodes() (#5274)
  • 2ab714b Merge branch 'master' into ast
  • 56eec0b AST: Update with latest changes from master (#5270)
  • f528e5e AST: numeric separators, BigInt (#5272)

There are 136 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 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.