-
Notifications
You must be signed in to change notification settings - Fork 93
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
create release for javascript #180
Comments
I am not terribly experienced with this myself, but I can share whatever wisdom I've acquired along the way. When you compile a library with Emscripten, all you get is a linux-standard As for applications themselves, you always need JavaScript to launch and manage the WASM code (how to handle memory; etc). At the lowest level, Emscripten can emit a |
I'm unlikely to get time to figure this out anytime soon, but just wanted to express interest in having more documentation around the WASM support, and in a perfect world bindings for NodeJS to make it easy to use from Javascript code. I currently use https://www.npmjs.com/package/js-yaml which works fine, but for my particular project parsing large YAML files makes up a large chunk of my integration test suite runtime (50%-60%) of total runtime, and I'd love to benchmark |
Since emscripten is now supported, I'd like to create the javascript artifacts as part of the release workflow.
Also, a quick JS usage example in the main README is needed.
@cschreib could you kick this off? I don't know much about JS or JS packaging, so maybe it would be better if you kick this off. I'd be happy to join in after the first changes. If you're currently taken and that is too much, could you at least provide some pointers on how to package?
The text was updated successfully, but these errors were encountered: