-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explore runtime linking of JS provider #19
Comments
This was referenced Sep 19, 2023
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This project is based on an older, but simpler way of building a js toolchain. We are statically compiling everything we need into one wasm file though a series of steps.
When javy switched hands to the bytecode alliance, they moved to a model of linking at runtime. Switching to this model could provide us some benefits. We've already effectively created a poor-man's linker to get exports to work. Supporting host functions would take us deeper down that path. So we either need to make use of a compile time linker or leverage wasmtimes runtime linker. We need some more research before we make a decision. One concern would be supporting other non-wasmtime runtimes. Will it work?
The text was updated successfully, but these errors were encountered: