Webpart is not beeing hosted

[ZzyzxIsAlreadyTaken]

Target SharePoint environment

SharePoint Online

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

💥 SharePoint Framework

Developer environment

None

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
• Version 135.0.3179.98 (Official build) (arm64)
• SPFx version
• 1.21
• Node.js version
• 22.15.0
• etc

Describe the bug / error

The web part is not built properly, or there is some referencing errors to manifests file.

If I manually copy the manifest file to the old location it will run so in one project I built a gulp task to copy it each time. But I will always get that warning message box that the web part will not appear in the toolbox.

Steps to reproduce

1. create a web part project
2. try to run it in hosted workbench
3. get no results

Expected behavior

no issues when running gulp serve --nobrowser

[jvanpiccs]

Hi, in my case the webpart its shown in the toolbox.

There is a previous similar issue here
#10053

Appears to be a problem between the workbench and this change with the manifests files locations. The workbench appears to be looking for the 2 locations, even if the location its found, the alert pop ups.

I'm downgrading to spfx 1.20 until the bug is fixed.

[Amey-MSFT]

Hello @ZzyzxIsAlreadyTaken,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[VesaJuvonen]

thx @jvanpiccs on providing great response for @ZzyzxIsAlreadyTaken. As noted - web part is there and this is a false message, but it's for sure confusing. This will be addressed with server side update, which starts rolling out to production gradually today and next week. Will be fixed automatically without client side updates.

[Ashlesha-MSFT]

@jvanpiccs , @ZzyzxIsAlreadyTaken ,
The underlying issues related to the workbench warning and manifest handling have now been resolved in the latest updates.

Could you please confirm if everything is working correctly on your side now?
If so, please go ahead and close the issue.

Thank you!

[Ashlesha-MSFT]

Closing as the resolution has been confirmed. #10053 (comment)