Skip to content

Conversation

nevkontakte
Copy link
Member

These changes make gopherjs work correctly in environments with fake $global.process object, which may be missing some of the properties. Specifically, when Go's wasm_exec.js is used, it fakes that object, but only partially. So if a gopherjs program was loaded in the same context as a Go wasm program, gopherjs would throw an undefined property exception.

These changes make gopherjs work correctly in environments with fake
`$global.process` object, which may be missing some of the properties.
Specifically, when Go's `wasm_exec.js` is used, it fakes that object,
but only partially. So if a gopherjs program was loaded in the same
context as a Go wasm program, gopherjs would throw an undefined property
exception.
@nevkontakte nevkontakte merged commit df0fbb1 into gopherjs:master Feb 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants