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

[browser][config] Reading runArgs available only on browser #81416

Open
ilonatommy opened this issue Jan 31, 2023 · 4 comments
Open

[browser][config] Reading runArgs available only on browser #81416

ilonatommy opened this issue Jan 31, 2023 · 4 comments
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono blocked Issue/PR is blocked on something - see comments runtime-mono specific to the Mono runtime
Milestone

Comments

@ilonatommy
Copy link
Member

Fetch function is not available on nodeJS < 18 (unless additional packages are installed) and even on 18 it's in experimental mode.
We want to use fetch to read runArgs.json. Currently #77719 enabled reading it only on browser, so that debugging libraries will be done correctly.

NodeJS is shipped with emcc and the latest emcc 3.1.30 has still an old Node = 14.18. Here is a PR to update it o v=15: emscripten-core/emsdk#829.
Officially, even Node 16 is already out of support.
According to @radekdoulik, trying to update Node to v=18 on Ubuntu 18.04 was not successful because it has too old libs. Ubuntu 20.04 is already fine, so for this OS we could upgrade when the end of support for Ubuntu 18 comes - April 2023.
Not sure what could be the plan for Windows.

@ghost ghost added the untriaged New issue has not been triaged by the area owner label Jan 31, 2023
@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@ilonatommy ilonatommy added arch-wasm WebAssembly architecture runtime-mono specific to the Mono runtime and removed untriaged New issue has not been triaged by the area owner labels Jan 31, 2023
@ghost
Copy link

ghost commented Jan 31, 2023

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

Fetch function is not available on nodeJS < 18 (unless additional packages are installed) and even on 18 it's in experimental mode.
We want to use fetch to read runArgs.json. Currently #77719 enabled reading it only on browser, so that debugging libraries will be done correctly.

NodeJS is shipped with emcc and the latest emcc 3.1.30 has still an old Node = 14.18. Here is a PR to update it o v=15: emscripten-core/emsdk#829.
Officially, even Node 16 is already out of support.
According to @radekdoulik, trying to update Node to v=18 on Ubuntu 18.04 was not successful because it has too old libs. Ubuntu 20.04 is already fine, so for this OS we could upgrade when the end of support for Ubuntu 18 comes - April 2023.
Not sure what could be the plan for Windows.

Author: ilonatommy
Assignees: -
Labels:

arch-wasm, runtime-mono

Milestone: -

@lewing
Copy link
Member

lewing commented Jul 21, 2023

Is this fixed now?

@ilonatommy ilonatommy added the blocked Issue/PR is blocked on something - see comments label Jul 24, 2023
@ilonatommy ilonatommy modified the milestones: 8.0.0, Future Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono blocked Issue/PR is blocked on something - see comments runtime-mono specific to the Mono runtime
Projects
None yet
Development

No branches or pull requests

3 participants