You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
Issue
Currently the
wasm_exec.js
andwasm_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
andwasm_exec_node.js
to npm. Add built-in TypeScript definitions.Implementation
If this is selected to move forward, I can create a pull request.
The text was updated successfully, but these errors were encountered: