revamp with .net 8

[elringus]

Complete rewrite using improved .NET 8 WASM capabilities and new JavaScript interop.

Changed

• Package name changed to Bootsharp.
• All the package-specific MSBuild properties got "Bootsharp" prefix to prevent conflicts; eg BootsharpEmbedBinaries.
• Event.getLast() changed to Event.last.
• Enums are now serialized as numbers by default (prev. strings). This can be changed via Bootsharp.Serializer.Options in C#. Enum names can still be accessed in JS, eg: ​​​​​​​

  enum MyEnum { Foo, Bar } // C#

  MyEnum[MyEnum.Foo] === "Foo" // JS

Improved

• The package now uses stock .NET runtime. (resolves #20, resolves #17)
• Multithreading is now supported. (resolves #79)
• AOT compilation is now supported. Package itself is now completely free of dynamic code and fully AOT-compatible.
• Trimming is now supported. With aggressive trimming enabled, minimal compressed build size is 744 KB.
• Stream-compiling WASM module is now supported.
• ES module is now produced instead of UMD, providing support for modern consumption scenarios in both browsers and JavaScript runtimes (node, deno, bun and VS Code web extension were tested). (resolves #53)
• Internal JSON serializer now works in source generation mode and doesn't use reflection.
• New JavaScript interop doesn't use reflection and allows direct transfer of common data types (byte, int, bool, char, string and arrays of them); only custom data structures are serialized to JSON. (resolves #75, resolves #51, resolves #19)
• Added extensions on Microsoft.Extensions.DependencyInjection for automatic injection and instantiation of the generated interop implementations (via standalone package).
• Event.last now returns all the arguments of the last broadcast (previously returned only the first one).
• When invoking a C# API while the runtime is not booted or invoking JavaScript binding which has not been assigned, an error with the endpoint is thrown. (resolves #26)

Fixed

• Publishing to custom output path. (fixes #112)
• Defining bindings in non-entry assemblies. (fixes #23)
• Disposing runtime WASM module resources. (fixes #22)

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (eb045ae) 100.00% compared to head (797655b) 100.00%. Report is 1 commits behind head on main.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #123 +/- ## ========================================= Coverage 100.00% 100.00% ========================================= Files 49 43 -6 Lines 1537 1439 -98 Branches 157 234 +77 ========================================= - Hits 1537 1439 -98 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[Aragas]

Any ETA on the merge?

[elringus]

Any ETA on the merge?

Hopefully by the end of the year. Planned to finish before .NET 8 GA, but got distracted with a side hustle. Though, it's already fully functional: I've migrated my own projects and everything seem to be working fine. Here are the latest packages if you'd like to try it out: bootsharp.zip.

[Aragas]

Hopefully by the end of the year. Planned to finish before .NET 8 GA, but got distracted with a side hustle. Though, it's already fully functional: I've migrated my own projects and everything seem to be working fine. Here are the latest packages if you'd like to try it out: bootsharp.zip.

Thanks for the packages! I was able to test the generation, but I'm not sure if it generated the desired outcome. Basically, it generates bin\Debug\net8.0\browser-wasm\AppBundle, but using BootsharpPackageDirectory for a custom path where the end package should be copied seems not to work. Should the outcome be similar to what we had previously? The typescript declaration for the package and the wasm files?

[elringus]

Yes, it should be similar to how it's worked before. Check the samples: https://github.com/elringus/DotNetJS/tree/feat/revamp/Samples

[Problemkurs]

Many thanks for your effort. I'm amazed how you got this working as there is not much information available I found.

I have an issue when publishing a project with bootsharp: After sucessful compilation the process exists with error code "npx rollup bootsharp.js -o bootsharp.mjs -f es -g process,module --output.inlineDyn amicImports" + another message "Cannot find module 'node:process'". This happens when I build the samples (ex. Trimming ) as well as in my own projects I tried it with. Any idea what this might be?

[elringus]

@Problemkurs Make sure node v20 or later is in the system path. (https://nodejs.org)