3 ms·
This looks very cool! I have just a couple of wishes on top of this: - I wish the file format were JSON-based instead of YAML-based. Then you could import .fl
by spankalee 3y ago
This looks very cool!
I have just a couple of wishes on top of this:
- I wish the file format were JSON-based instead of YAML-based. Then you could import .flyde files with standard `{type: 'json'}` import attributes and not need fetch or a webpack loader.
- I wish the editor were distributed as web components so taht they could be easily embedded into any framework.
- gabigrin 3y agoThanks! I plan to move it to JSON sometime in the future, but it won't remove the need for a webpack loader, at least not the way it is built now. The webpack loader exists to resolve dependencies. If your flow depends on Node1 from @flyde/stdlib and Node2 from @spankalee/flyde-nodes, "something" needs to resolve the code for these nodes. A possible way around this is to bundle/compile a flow and its dependencies using tooling on Flyde's end, but that's just shifting what the loader does to another end of the pipeline :) Regarding shipping in a web component - you could always wrap https://www.npmjs.com/package/@flyde/flow-editorin https://www.npmjs.com/package/@flyde/flow-editorin a standalone renderer. It's cumbersome and adds many extra KBs, but doable. Appreciate the feedback!