You can use standard ASP.NET Core hosting and deployment methods. Unlike the development build, the production build doesn't require Node.js to be installed on the server. When you publish, the build configuration emits a minified, transpiled build of your client-side code. This is configured to happen automatically. In production, serve a version of your app that's optimized for performance. The app watches JavaScript, HTML, and CSS file changes on disk and automatically recompiles and reloads when it sees those files change. For example, JavaScript bundles include source maps (so that when debugging, you can see your original source code). In development, the app runs in a mode optimized for developer convenience. To install third-party npm packages, use a command prompt in the ClientApp subdirectory.

The app created by the template contains a Bootstrap-based layout and a basic routing example. There are slight differences between the React app created by this template and the one created by CRA itself however, the app's capabilities are unchanged. See the official CRA documentation for more information. The ClientApp directory is a standard CRA React app. The React app, residing in the ClientApp subdirectory, is intended to be used for all UI concerns. The ASP.NET Core app is intended to be used for data access, authorization, and other server-side concerns. The project template creates an ASP.NET Core app and a React app.

On the first run, the build process restores npm dependencies, which can take several minutes. Run dotnet build to verify your app builds correctly. On Linux or macOS, run export ASPNETCORE_ENVIRONMENT=Development. On Windows (in non-PowerShell prompts), run SET ASPNETCORE_ENVIRONMENT=Development. Subsequent builds are much faster.Įnsure you have an environment variable called ASPNETCORE_ENVIRONMENT with value of Development. The build process restores npm dependencies on the first run, which can take several minutes. csproj file, and run the app as normal from there.

Learn react js