Run your code in browser. Because why use brooms when you have hippogryphs?
Try it in development mode. Set the environment variable and then restart dotnet run. On Windows, that’s:
set ASPNETCORE_ENVIRONMENT=Development dotnet run
… or on Mac/Linux:
export ASPNETCORE_ENVIRONMENT=Development dotnet run
Now you can modify client-side resources in a text editor (e.g., some ts file, or a tsx file in a React app, or an .html file in a Knockout/Angular app), and see it auto-update immediately in the browser. This is the combination of Webpack dev middleware and Hot Module Replacement (HMR).
Make a production build. Set the ASPNETCORE_ENVIRONMENT variable to Production and then run:
webpack --config webpack.config.vendor.js
…to regenerate both the vendor and app bundles. Now when you run the app (dotnet run again), the browser will receive fully minified resources.
Hopefully it should be clear in the source folders where you can start to add new components to your app and make it your own.
Running with docker
docker build -t buckbeak . && docker run -p 5000:5000 -it -v /var/run/docker.sock:/var/run/docker.sock buckbeak