Hi @mcintyre321
Yes, there are instructions on running NetPad as a SPA Application in the CONTRIBUTING.md file, under Creating a development environment.

(Assuming you’ve already cloned the repo)

Steps to Run NetPad as a Web App

1. Install Dependencies and Start the Frontend

cd NetPad\src\Apps\NetPad.Apps.App\App

npm install && npm run start-web

2. Run the .NET Backend

cd NetPad\src\Apps\NetPad.Apps.App && dotnet run

3. Access NetPad in the Browser Once both parts are running, go to http://localhost:57940/ in your browser.

To access NetPad I believe you need to change the Url in appsettings.Development.json to http://0.0.0.0:57940 and forward that port.

Additional Notes

• System.Text.Json Warning: There’s a known issue with System.Text.Json. To suppress this warning temporarily, add NU1903 in the OmniSharp.NET.csproj file.

• Troubleshooting Tauri Shell Builds: If you encounter any build issues with the Tauri shell, try checking out the commit 8bf4fd7 as a workaround.

Thanks @SimonNyvall. I got your PR merged as well. I also fixed the security warning with System.Text.Json and updated the package.

@mcintyre321 did you get it running alright? To answer your question, yes it is possible. The instructions Simon left above is all you need. I plan on releasing a pre-built binary to run as a web app but for now you can easily run it from source.

A readonly mode sounds like a good idea for that use case. Noteworthy is NetPad currently has a single session/state. Different users would not get their own session. This means that if you host NetPad as a web app, every browser that connects to it will have the same tabs open, the same statuses for each script (running or not), the same output in the results pane...etc. If one user clicks to switch a tab, the tab is switched on every browser.

Its definitely on the roadmap to provide multi-user sessions (including auth) and give users the ability to create profiles as well.