It seems ComponentLoader fails to resolve component and graph paths on Windows, and so loading them doesn't work.
We should probably ensure we replace all slashes (/) with path.sep in ComponentLoader
Some related links:
As stated in Google Groups (https://groups.google.com/forum/#!topic/flow-based-programming/v7Wiiyys-Ik ): I'm willing to help but unable to run the tests as https://github.com/jdcataldo/grunt-mocha-phantomjs cannot be installed on windows.
I'm going to try to fix the paths, but I'm not as familiar as I should be with the noflo internals and coffeescript to be sure that I got it right.
I would be very thankful if someone with more expertise could replace the the slashes as @bergie suggested. I can verify if it works on windows if someone sends a PR.
@p0wl ok, just comment out the phantomjs dependency on package.json and the Gruntfile.coffee
We should note that this includes other subtle path issues, like #122
Doesn't seem to be a problem any longer. I just verified by running tests of a rather large NoFlo app on Node.js/Win8
FYI: If you need Windows based node.js CI testing there is now http://www.appveyor.com, it is very similar to Travis-CI except it is focussed on Microsoft platforms (but with node and github and a nice .yml setup etc).
@Bartvds thanks! Added
Seems path resolution is fine: these tests actually run a graph that depends on components from other libraries