Supposed to work?

[staeke]

Bumped into this project, which looks really cool. But...

• it seems unclear how this relates to thingamajig and amok. Are those old repos for the same code? Want to clarify
• it seems the npm package doesn't contain any code
• loading the liveflowjs over network just yields

Uncaught DOMException: Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'http://liveflow.js.org/liveflow.js'.

...so am I missing something?

[caspervonb]

In short, no its not in a release yet but it does work (video of what can be done if the stars are aligned and everything goes smoothly) however I've kept quiet about it on purpose as I don't consider it ready for public consumption just yet.

it seems unclear how this relates to thingamajig and amok. Are those old repos for the same code? Want to clarify

Amok worked via the debugging protocol, this feature is now in chrome itself (add your files to a workspace, and your source files will be watched allowing you to edit functions on the fly from any editor Note: no execution takes place, only functions get swapped.

This is Thingamajig.js (which was a working name), and its approach is different from Amok in that this aims to enable "progressive evaluation" of scripts, so functions are swapped like the chrome only debugger "live edit" implementation but it also evaluates new code, getting the values of the old code from cache so each file effectively becomes a REPL where each top level statement is executed exactly once (in other words, you can install new event handlers etc which is typical of JS APIs in already running programs).

it seems the npm package doesn't contain any code

Still in pre-release, reserved the package name during the rename from thingamajig -> liveflow, the current dist for web is available via https://liveflow.js.org/liveflow.js

loading the liveflowjs over network just yields

Any details on that? my first guess would be a CORS issue?