Closed bergie closed 7 years ago
@jonnor currently build is failing due to microflo-empscripten issues. Would be nice to fix those
Uhm, cannot find module ws
- that is a very odd message. Is fbp-manifest
or something including microflo-runtime.js
. If so, why? That probably wont work
@bergie ^ see above command
Both microflo and microflo-emscripten are in package deps https://github.com/flowbased/fbp-protocol-client/blob/master/package.json
Problem is that webpack
or something is failing on this third-party dep, which is deep inside some generated Emscripten code. It looks all be optional but I don't know how to disable it.
I don't see any other required deps which are not node.js standard though, so maybe just add commonjs ws
so webpack does not fall over?
Of course the issue with webpack is that this may be needed by every dependency down...
The hacky way is of course to just include ws
...
Wait, let me try to remove some unused #include
statements, maybe that will help Emscripten to not generate this code. It looks to be for standard I/O streams
@bergie no luck, reduced includes to a minimum and still the require('ws')
code is there
@bergie do you want me to add ws
as a dependency to microflo-emscripten
in the meantime? It is actually very small, few subdeps, nothing native.
The offending code is gone when compiling with latest Emscripten, but that is impossible to setup on Travis CI so not planning on that anytime soon...
@jonnor well, we need to get this back to releasable shape, so do whatever you must.
@jonnor next error: https://travis-ci.org/flowbased/fbp-protocol-client/builds/190673694#L390
@bergie the ws
dependency is now included, but it does not fix it because webpack does not look in subdirs. You need to use NPMv3. This will basically affect all projects using grunt-noflo-browser
due to the webpack limitation...
Fixes Flowhub React example