Version 2.3.0 of grunt-contrib-uglify just got published.

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

As grunt-contrib-uglify 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 💪

Your Greenkeeper Bot 🌴

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

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.

Your Greenkeeper Bot 🌴

The devDependency webpack was updated from 4.35.3 to 4.36.0.

🚨 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.

Your Greenkeeper Bot 🌴

Previous tests were written with noflo-test library. Added components from noflo are written in nodeunit. Need to re-write the two to conform with new noflo testing method (i.e. Jasmine).

We need to use new template from grunt-init-noflo in place of legacy structure.

i am facing a problem with similar components of SplitStr.coffee
i use this component in browser.
inport receive data packets from other component and for delimiter i set space characters. so i type space in delimiter in browser.
but when i run graph SplitStr.coffee use "\n" default value at first run.
but when i rerun without refresh this component use space for delimiter. when i refresh page and run it use default one again.

how to fix
thanks

Right now the noflo version used is an arbitrary version made to work. Upgrade to v0.4.0 as soon as it's ready.

Version 0.8.1 of noflo just got published.

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

As noflo is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

The noflo-test based tests are currently failing: https://travis-ci.org/noflo/noflo-strings/builds/69503391
With NoFlo 0.5.9 it however works https://travis-ci.org/noflo/noflo-strings/builds/36458976

This seems to be due to noflo-test not being compatible with newer. Possibly due to noflo/noflo-test#12
That is now fixed, however the library broke API when moving to Mocha. discuss is now describe and one must additionally use it. Neccesitating rewriting the tests in noflo-string to match (and releaseing a new noflo-test)

It seems to me that SendString is generating a null ahead of its output... unpredictably. It was doing it quite consistently until I modified the diagram - then it stopped doing it... then when I reconfigured the diagram, it started doing it again. So, why would SendString change from generating an extra null to not doing it, and then to doing it again, when the network is reconfigured?

I added a component which prefixes a number in front of the output line, and got the following output (when the null was happening):

  0:null
  1:Joe 
  2:Mary 

Additional information: the 'string' port is receiving 3 character strings; the 'in' port is receiving 3 HTMLLIElements; the 'out' port is emitting a null, followed by the first 2 strings, dropping the third.

Flowhub note: when I click on the output connection from SendString, I don't see the (naked) null string - there should be some indication, e.g. a special icon.

PS Where is SendString documented?