-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Minimizing size of Dotnet WebAssembly Browser app #87617
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsHello, I have Dotnet WebAssembly Browser app. The size of default dotnet.native.wasm with .Net 8 preview 5 is 2.8 MB. On other hand In blazor WebAssembly app we can have PublishTrimmed and TrimMode to reduce the size to 300-400 KB. These 2 properties do not have effect on Web Assembly Browser app. Trimming doesn't takes place. Also Is there way to trim timezone and other data. Is there any way to allow trimming to get smaller dotnet wasm in Web assembly browser application? Is there any roadmap for it similar to blazor size reduction tasks? Thanks
|
Are you publishing the app? Is PublishTrimmed set to true? |
Yes , I used these flags in csproj. |
Both I got the same size for You can disable globalization with The timezone data has ~ 300KB which is not trimmable at the moment. With brotli compression it should get to ~ 400 KB. |
This issue has been marked |
@maraf Thanks for this valuable information. |
I'm happy to help! I'm going to close this issue, feel free to reopen it or open a new one if you have further questions. |
Hello, I have Dotnet WebAssembly Browser app. The size of default dotnet.native.wasm with .Net 8 preview 5 is 2.8 MB.
On other hand In blazor WebAssembly app we can have PublishTrimmed and TrimMode to reduce the size to 300-400 KB. These 2 properties do not have effect on Web Assembly Browser app. Trimming doesn't takes place. Also Is there way to trim timezone and other data.
Is there any way to allow trimming to get smaller dotnet wasm in Web assembly browser application? Is there any roadmap for it similar to blazor size reduction tasks?
Thanks
The text was updated successfully, but these errors were encountered: