core
core copied to clipboard
dotnet-websharper
Releasing WebSharper 6.x-net8 variants
👋 Would it be possible to also get a -net8 of the latest version of the packages in 6? There's been a couple updates and would be nice to get a 6.1.7.476-net8 (or equivalent).
@TheAngryByrd Are you referring to FCS or WebSharper updates? Would it make things easier if we released WS8 (the generated output is massively different, but there shouldn't be too many breaking changes)? The only major pending roadblock for WS8 is in the WS project templates (sitelets in debug mode).
Are you referring to FCS or WebSharper updates? The Websharper.FSharp package:
- https://www.nuget.org/packages/WebSharper.FSharp/#versions-body-tab
- https://nuget.info/packages/WebSharper.FSharp/6.1.7.476
- Contains the TFM for net6.0 while https://nuget.info/packages/WebSharper.FSharp/6.1.7.441-net8 contains net8.0.
The issue comes to requiring needing 6.0 installed to run it and it will end support In November
Would it make things easier if we released WS8 (the generated output is massively different, but there shouldn't be too many breaking changes)? The only major pending roadblock for WS8 is in the WS project templates (sitelets in debug mode).
I don't think we rely on sitelets, so we'd be willing to try it for sure! Thanks! 😄
As dotnet 6 is EOL, it might make sense to make the -net8 the default generated package?
There are many (several dozen) WebSharper 6 libs that have not yet been ported to WebSharper 8, so in a way it would almost make sense to provide net8 NuGets for everything in WebSharper 6.x. However, this would quickly turn into a massive time sink, maintaining a parallel universe for backward compatibility and a flavor of developer experience that "aims to expose you to JS as little as possible", next to the new WebSharper 8+ universe.
WebSharper 8 does need dealing with JavaScript tooling in a few well-defined places (fetching dependencies, bundling, etc.), but it outputs JSM code that turns out to be quite friendly to eventually plugging back in a WS6-like automagic experience. But we need to get there and it needs a lot of input!
All in all, if you are using WebSharper 6, please try out WebSharper 8 beta (from the GitHub feed - and soon on NuGet), and let us know of any issues you run into. Thanks!