Skip to content
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

proposal: syscall/js: publish wasm_exec.js and wasm_exec_node.js bindings to npm #58250

Open
russellsteadman opened this issue Feb 2, 2023 · 1 comment

Comments

@russellsteadman
Copy link

Issue

Currently the wasm_exec.js and wasm_exec_node.js files for executing WASM builds have to be manually added to JavaScript projects. This creates versioning issues, type issues for TypeScript projects, and is not a normal workflow for larger projects.

Solution

Create and publish a package containing wasm_exec.js and wasm_exec_node.js to npm. Add built-in TypeScript definitions.

Implementation

If this is selected to move forward, I can create a pull request.

@russellsteadman russellsteadman changed the title syscall/js: publish wasm_exec.js and wasm_exec_node.js bindings to npm proposal: syscall/js: publish wasm_exec.js and wasm_exec_node.js bindings to npm Feb 3, 2023
@gopherbot gopherbot added this to the Proposal milestone Feb 3, 2023
@ianlancetaylor ianlancetaylor moved this to Incoming in Proposals Feb 8, 2023
@Zxilly
Copy link
Member

Zxilly commented Aug 29, 2024

But these files are not as new as they are; instead, they should correspond precisely to the version of Go being used.
Probably copying the files from misc/wasm during the build process would be a better choice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Incoming
Development

No branches or pull requests

4 participants