Jimmy Byrd

Main benefit (I think) is I can then debug in vscode by setting [sourceMapPathOverrides](https://github.com/Microsoft/vscode-chrome-debug/blob/master/README.md#sourcemaps) (yes that debugger is archived but the current extension doesn't have this documented well). I can...

no worries!

@vzarytovskii were the updates to those dependencies required?

> In theory, we could bump up the .NET SDK requirement for WebSharper 6, but .NET SDK 7 is not LTS so we should investigate/reconsider first. Now that .NET 8...

Thanks for all the feedback! I ended up with the `|> Array.map (Option.defaultValue null)` for now.

Well I guess I want to end up with this as my dependency tree on nuget when I go to pack it ``` Dependencies .NETFramework 4.5 FSharp.Core (>= 4.0.0.1) .NETStandard...

As .net 5 is the way forward, I'm gonna close this.

Everything is going to be .NET 5. There won't really be a .NET core or .NET framework.

I'm not concerned with supporting super old versions of frameworks. [This post](https://blog.marcgravell.com/2020/01/net-core-net-5-exodus-of-net-framework.html) covers some similar thoughts I have about supporting older frameworks.

Why are you removing Newtonsoft entirely? I can see maybe swapping the default but not outright removal.