Please add support to Blazor WASM as SPFX WebPart framework

[omarceloribeiro]

What type of issue is this?

other

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Target SharePoint environment

SharePoint Online

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

• browser version: Edge latest Version 115.0.1901.200 (Official build) (64-bit)
• SPFx version 1.17.4
• Node.js version 16.20.2
• etc

Issue description

Would be great build spfx webpart using blazor as the framework. on webpart creation just select blazor and all the folder/project is generated. Would be a great improvement on spfx development for the community developers. would be a good option to build webparts like employee bithdays, company next events, current wheater, current pending approvals, company city holidays, etc.

I have this repository where I am working on it:

https://github.com/omarceloribeiro/spfxblazorwebpart

see the demo video:
https://github.com/omarceloribeiro/spfxblazorwebpart/blob/main/DemoVideo.md

but still has some issues about the compatibility with SharePoint site and SharePoint AppCatalog deployment.

For example is not possible to deploy files to a subfolder in SharePoint AppCatalog
#9150

User voice ticket open:

https://techcommunity.microsoft.com/t5/sharepoint-developer/please-add-support-to-blazor-in-spfx-webpart/m-p/3918870

thank you!

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[omarceloribeiro]

fixed issues on navigation
added a video
https://github.com/omarceloribeiro/spfxblazorwebpart/blob/main/DemoVideo.md

[omarceloribeiro]

Updated the issue description, added the link to user voice ticket. changed the description to be similar to the request on user voice.

[anghelnicolae]

Any updates on this? Is Microsoft looking into it? This might be an easier workaround for SPFx compatibility issues with newer TypeScript/React/NodeJS versions on SharePoint on-premise.

[github-actions]

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.