3 Commits

Author	SHA1	Message	Date
Victor Costa	bd61913973	wasm: patch wasm_exec.js and wasm_exec_node.js from Go 1.18+ (#5483) ... * wasm: patch wasm_exec.js and wasm_exec_node.js from Go 1.18+ Port this commit https://github.com/golang/go/commit/680caf15355057ca84857a2a291b6f5c44e73329 removing polyfills from `wasm_exec.js`, now the environment is expected to provide all the required polyfills. `wasm_exec.js` now only provides stub fallbacks for globalThis.fs and globalThis.process. All NodeJS specific code is now in a separate file `wasm_exec_node.js` with its required polyfills. * feat: bump minimum node version to 22 Drops official support for NodeJS 18 for WASM by removing the provided polyfills in the `wasm_exec.js`. Now the environment is expected to provide the polyfill if it is running on older NodeJS versions The new minimum required version for WASM is NodeJS 22+. * chore: removed wrong comment `wasm_exec_node.js` no longer contains the polyfill for NodeJS 18	2026-07-08 12:32:00 +02:00
Ayke van Laethem	612a38e363	wasm: don't block //go:wasmexport because of running goroutines ... This fixes bug https://github.com/tinygo-org/tinygo/issues/4874.	2025-04-29 14:19:17 +02:00
Ayke van Laethem	4ef5109a07	wasm: add //go:wasmexport support to js/wasm ... This adds support for //go:wasmexport with `-target=wasm` (in the browser). This follows the //go:wasmexport proposal, meaning that blocking functions are not allowed. Both `-buildmode=default` and `-buildmode=c-shared` are supported. The latter allows calling exported functions after `go.run()` has returned.	2024-10-18 10:07:21 +01:00