https://github.com/maraf/blazor-wasm-react
Blazor WebAssembly + React
https://github.com/maraf/blazor-wasm-react
Last synced: 4 months ago
JSON representation
Blazor WebAssembly + React
- Host: GitHub
- URL: https://github.com/maraf/blazor-wasm-react
- Owner: maraf
- License: mit
- Created: 2025-07-10T07:32:14.000Z (12 months ago)
- Default Branch: main
- Last Pushed: 2025-07-11T11:16:39.000Z (11 months ago)
- Last Synced: 2025-09-17T00:07:30.453Z (9 months ago)
- Language: JavaScript
- Size: 2.88 MB
- Stars: 1
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Blazor WASM in a React application
This sample shows how to use Blazor WebAssembly integrated into a React application.
- [Blazor Community Standup - Integrate .NET in JavaScript apps](https://www.youtube.com/watch?v=tAh899Gri4E)
- [.NET + React demo](https://github.com/maraf/dotnet-wasm-react)
## Project structure
- **app**: target React application using rollup to do the JavaScript build
- **blazor**: Blazor WebAssembly application containing several components
## Live demo
https://maraf.github.io/blazor-wasm-react/
## Building source code
### Blazor components
- Install .NET 10 SDK (preview7+)
- Run `dotnet publish` in the `blazor` folder
### App
In the `react` folder
- Run `npm install`
- Run `npm run build`
### Under the hood
In .NET 10 we have added a way to produce JavaScript bundler friendly build output. In JavaScript world, file dependencies (like other JS files or images) are resolved using import statements.
In browser world, only JavaScript files can be imported using import statements. Because of this, we introduced an MSBuild property `WasmBundlerFriendlyBootConfig=true` to switch between browser-runnable output
and JavaScript bundler-friendly build output. Switching this on allows JavaScript bundlers to consume output of .NET build (publish).
.NET build (`dotnet build` or Build in VS) doesn't copy all files to the output directory. This happens only for publish. We do it make incremental builds faster. As a result, integrating .NET build output into JavaScript bundlers work properly for publish output. Making it work for build output should be possible by properly mapping imports to individual locations using rollup (or other bundler) custom plugin. We don't provide such plugin at the moment.