Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

@elringus
Copy link
Owner

@elringus elringus commented Sep 4, 2023

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

Fixed

@github-actions github-actions bot added the stale Auto-closing due to inactivity label Nov 14, 2023
Repository owner deleted a comment from github-actions bot Nov 14, 2023
@elringus elringus added enhancement New feature or enhancement and removed stale Auto-closing due to inactivity labels Nov 14, 2023
@Aragas
Copy link
Contributor

Aragas commented Nov 22, 2023

Any ETA on the merge?

@elringus
Copy link
Owner Author

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
Copy link
Contributor

Aragas commented Nov 28, 2023

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
Copy link
Owner Author

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

@Problemkurs
Copy link

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
Copy link
Owner Author

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

@elringus elringus merged commit 999f371 into main Dec 31, 2023
@elringus elringus deleted the feat/revamp branch December 31, 2023 20:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Morty Proxy This is a proxified and sanitized view of the page, visit original site.