-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Integrating .NET 8 WebAssembly project into the Angular app #88545
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsIs there a nice way to incorporate the dotnet JS runtime into an existing angular project? I manage to do that with .NET 7 files but it was tricky still. When imported dotnet.js assumes it's run in a node environment so it tried loading fetching all files from the config .JSON using file system paths. I ended up messing about with the source code to rewrite the filesystem paths to URLs and it worked, but that seems like a dirty hack. With .NET 8 there are more that just dotnet.js files - I can see it's trying to dynamically import dotnet.runtime.js and dotnet.native.js - that is where Webpack is having issues with importing these.
|
hi @socreative, we are aware of it, we collect use cases here #86162 I will close this issue as duplicate. |
I fixed webpack sample we have #88907 True single file solution would take more effort in linked issue. |
Thanks. An npm package to replace dotnet.js would be an ideal scenario so it could be intergrated with front-end or node apps so. |
Is there a nice way to incorporate the dotnet JS runtime into an existing angular project?
I manage to do that with .NET 7 files but it was tricky still. When imported dotnet.js assumes it's run in a node environment so it tried loading fetching all files from the config .JSON using file system paths. I ended up messing about with the source code to rewrite the filesystem paths to URLs and it worked, but that seems like a dirty hack.
With .NET 8 there are more that just dotnet.js files - I can see it's trying to dynamically import dotnet.runtime.js and dotnet.native.js - that is where Webpack is having issues with importing these.
The text was updated successfully, but these errors were encountered: