It's probably helpful to have some background context for the development of this
The author of this library is also the author of the React JUCE renderer. It's a toolkit that re-uses React Native's rendering engine to allow you to use JS and React to render JUCE components:
So at this point, you have a (presumably) C++ JUCE app that is using JS/TS to render the UI. Why not work to move DSP stuff into JS as well, so that you're gluing minimal bits of C++ together?
It's not a far leap from there to here when you follow this line of thinking down the road.
The author of this library is also the author of the React JUCE renderer. It's a toolkit that re-uses React Native's rendering engine to allow you to use JS and React to render JUCE components:
https://www.nickwritesablog.com/blueprint-a-juce-rendering-b...
https://github.com/JoshMarler/react-juce
So at this point, you have a (presumably) C++ JUCE app that is using JS/TS to render the UI. Why not work to move DSP stuff into JS as well, so that you're gluing minimal bits of C++ together?
It's not a far leap from there to here when you follow this line of thinking down the road.