There are several docs around intro to JSI, but they mainly are in the context of React Native. Our paradigm is different, as we aim to extend the JSI to the JVM to enable "direct" (at least through JNI) integration with the native JavaScript Runtime implementations. This way, we can connect it to our existing JS abstraction (Node & Runtime) for use within Player without having to change any of the Player code. This is a realization of the goals for that abstraction piece, and really, I see that abstraction piece as a parallel to the native JSI definition. We'll likely want to converge the two abstractions and maybe even position this as bringing JSI to the JVM.
For diving in, start with the JVM JSI definitions and see how they're used in the tests (relies on HermesRuntime):
Initial groundwork for using the Hermes runtime on the JVM. There are a few parts to this PR:
What we're aiming for (some slight inaccuracies): https://gist.github.com/sugarmanz/d07d443f24f6eee1db9ac1c7ba1681c1
Some helpful links:
There are several docs around intro to JSI, but they mainly are in the context of React Native. Our paradigm is different, as we aim to extend the JSI to the JVM to enable "direct" (at least through JNI) integration with the native JavaScript Runtime implementations. This way, we can connect it to our existing JS abstraction (
Node&Runtime) for use within Player without having to change any of the Player code. This is a realization of the goals for that abstraction piece, and really, I see that abstraction piece as a parallel to the native JSI definition. We'll likely want to converge the two abstractions and maybe even position this as bringing JSI to the JVM.For diving in, start with the JVM JSI definitions and see how they're used in the tests (relies on
HermesRuntime):Value.ktdefinitions.Change Type (required)
Indicate the type of change your pull request is:
patchminormajorDoes your PR have any documentation updates?