V6 release

[Larocceau]

.NET 10 will be released in November 2025; let's try to release SAFE 6 as close to that as possible!

These todos have been copied from the previous release issue: #569

• [ ] Upgrade SDK to .NET 10
• [ ] Upgrade runtime to .NET 10
• [ ] Update Fable dependencies
• [ ] Verify minimal template
• [ ] Verify Azure deployment
• [ ] Update release notes and versions
• [ ] Release template
• [ ] Update docs

Additionally:

• [ ] Upgrade to fable 5 (currently in alpha)
• [ ] Use vite plugin for fable?

[Larocceau]

It seems like Paket has not started working on net10 support, but looking at previously released versions, it should not be too hard. I'll create a ticket there!

[Freymaurer]

Hey! I just upgraded a larger safe stack to tw4 and daisyui5, just wanted to make you aware of an issue i encountered.

The issue

I added a new tw/daisyui class, previously not used anywhere in the app. Class was correctly applied to the html node (verfied, via inspector), but no styling was applied. Tailwind did not generate the required css classes.

Only on a restart (therefore, rebuild) changes were correctly applied

The solution

To get nice HMR we need to ignore fsharp files in server.watch vite.config. The new tailwind setup with vite-plugin uses this very same watchmode also to check for updates in class names.

server: {
        watch: {
            ignored: ["**/*.fs"]
        },
    },

With the fs files ignored, we now need to watch js files. In the official tailwind docs we can find that files on .gitignore are by default ignore for class names (link). Because of this we need to register the src/Client/output folder explicitly. But this only re-registers the folder. If the underlying files are still on the .gitignore they are still not watched. In the .gitignore comment out *.fs.js (about the *.fs.js, i am not 100% sure. MY setup is a bit different, so maybe test it out)

@import "tailwindcss";
@source "./output/";

# *.fs.js
*.fs.js.map
output/

Hope this will help!