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.

Sign up for GitHub

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

Jump to bottom

Developers can run .NET libraries inside Node.js #47336

Closed
1 task done
marek-safar opened this issue Jan 22, 2021 · 12 comments · Fixed by #62779
Closed
1 task done

Developers can run .NET libraries inside Node.js #47336

marek-safar opened this issue Jan 22, 2021 · 12 comments · Fixed by #62779
Assignees
@pavelsavara
Labels
arch-wasm WebAssembly architecture area-Meta needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration tracking This issue is tracking the completion of other related issues.
Milestone
Future

Comments

@marek-safar
Copy link
Contributor

Node.js sports V8 engine which means it can run WebAssembly code. In the recent Node.js v15.6.0 version initial WASI support was added to further support WASM.

Developers which would like to run .NET code inside Node.js would use publish for wasm target. This will probably mean adding a new RID in form of node-wasm or wasi-wasm.

Related issues
@marek-safar marek-safar added the User Story A single user-facing feature. Can be grouped under an epic. label Jan 22, 2021
@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Jan 22, 2021
@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.

@marek-safar marek-safar added the arch-wasm WebAssembly architecture label Jan 22, 2021
@ghost
Copy link

ghost commented Jan 22, 2021

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

Issue Details

Node.js sports V8 engine which means it can run WebAssembly code. In the recent Node.js v15.6.0 version initial WASI support was added to further support WASM.

Developers which would like to run .NET code inside Node.js would use publish for wasm target. This will probably mean adding a new RID in form of node-wasm or wasi-wasm.

Related issues

Author: marek-safar
Assignees: -
Labels:

User Story, arch-wasm, untriaged
Milestone: -

@marek-safar marek-safar added this to the Future milestone Jan 22, 2021
@marek-safar marek-safar removed the untriaged New issue has not been triaged by the area owner label Jan 22, 2021
@krwq krwq added the untriaged New issue has not been triaged by the area owner label Feb 4, 2021
@lewing lewing added untriaged New issue has not been triaged by the area owner and removed untriaged New issue has not been triaged by the area owner labels Feb 5, 2021
@lewing
Copy link
Member

lewing commented Feb 5, 2021

node-wasm, wasi is very different. What are we using untriaged to mean here?

@danmoseley
Copy link
Member

@lewing this story needs an epic parent.

@marek-safar
Copy link
Contributor Author

marek-safar commented Feb 5, 2021 •
edited
Loading

@danmosemsft it has Future milestone (intentionally)

@joperezr joperezr removed the untriaged New issue has not been triaged by the area owner label Feb 9, 2021
@marek-safar marek-safar added tracking This issue is tracking the completion of other related issues. and removed User Story A single user-facing feature. Can be grouped under an epic. labels Feb 11, 2021
@jaykrell
Copy link
Contributor

Is this really node-specific, or just wasi?

@ghost ghost added the needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration label Feb 19, 2021
@joperezr joperezr removed the needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration label Mar 2, 2021
@orengor
Copy link

orengor commented Mar 9, 2021

+1 on this request from Excel Online.
We have a scenario where we would like to run .NET libraries from a Node.js microservice.

@ghost ghost added the needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration label Mar 9, 2021
@joperezr joperezr removed the needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration label Mar 10, 2021
@Daniel-Genkin
Copy link
Contributor

I am working on adding NodeJS support. I would appreciate your feedback
PR: #54640

@ghost ghost added the needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration label Jun 23, 2021
@thaystg thaystg linked a pull request Jul 13, 2021 that will close this issue
[WASM] Adding a new switch to run wasm on NodeJS #54640
Closed
7 tasks
@andersson09
Copy link

I am working on adding NodeJS support. I would appreciate your feedback PR: #54640

Is this PR supporting WASI?

@lewing
Copy link
Member

lewing commented Dec 1, 2021

I am working on adding NodeJS support. I would appreciate your feedback PR: #54640

Is this PR supporting WASI?

No, wasi support has different complications. We don't have firm plans to support it yet but we're doing some exploratory work.

@andersson09
Copy link

Cool and are you exploring compiling mono to wasi or just aot or both?

@pavelsavara pavelsavara self-assigned this Dec 6, 2021
@pavelsavara pavelsavara mentioned this issue Dec 6, 2021
Merged
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Dec 6, 2021
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Dec 16, 2021
@pavelsavara pavelsavara mentioned this issue Dec 16, 2021
Merged
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Dec 16, 2021
Repository owner moved this from Future to Done in Triage POD for Reflection, META, etc. Dec 18, 2021
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Dec 18, 2021
@elringus elringus mentioned this issue Dec 23, 2021
Closed
@pavelsavara
Copy link
Member

+1 on this request from Excel Online. We have a scenario where we would like to run .NET libraries from a Node.js microservice.

@orengor do you need wasm runtime or JS <->dotnet-x64 interop would be actually better?

@ghost ghost locked as resolved and limited conversation to collaborators Feb 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@pavelsavara pavelsavara

Labels
arch-wasm WebAssembly architecture area-Meta needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration tracking This issue is tracking the completion of other related issues.
Projects
No open projects
Triage POD for Reflection, META, etc.
Status: Done
Milestone
Future