The best way to develop functional-first web applications.

Joined September 2017
The new SAFE.Server and SAFE.Client packages also simplify your dependencies by giving you a basic "known-good" set of dependencies. Of course this will work with the NuGet client, and you can use this with your own hand-rolled SAFE apps if you like!
1
5
376
This also affords us a great opportunity to improve documentation within the editor, with links to useful articles and recipes. We're going to continue to build upon this in future releases.
1
1
3
409
With the latest release of the SAFE Template, we've added support for client and server NuGet packages which come with handy types and functions to help you get up and running even more quickly, using best practices. nuget.org/packages/SAFE.Temp…
1
9
24
2,029
4. Navigate to localhost:8080 - your application is now running!
1
225
3. Run your application. A simple dotnet run will compile and launch both server and client, all pre-configured to talk to one another.
1
56
2. Create a new directory for your application, and within it create your new SAFE app.
1
60
Upgrading to and running your first SAFE Stack v5 is easy, thanks to @dotnet SDK and its templating support - just follow these 4 simple steps! 1. Install the latest template. If it already exists, it'll be upgraded automatically.
1
4
14
1,437
Good news everyone! SAFE Stack v5 launched over the weekend. You can get it on @nuget right now! #fsharp #dotnet #web #javascript #react nuget.org/packages/SAFE.Temp…
1
6
312
This was one of the main reasons SAFE Stack was created: Lowering the barrier to entry for web developers who want to see the benefits of FP first hand, or F# developers who until now never felt able to create web applications.
1
3
14
Did you know that the latest versions of @VisualStudio now support the @safe_stack template directly? Just make sure the template is installed and turn on "Show all .NET Core Templates..." in the Preview Features options pane in VS! #fsharp #web @dotnet
16
47