Sharepoint out of the box Hello World webpart just fails

[mfornaris]

I followed all steps for creating a project to develop a SPFx webpart, here my env:

node -v: v22.22.3 yo --version: 7.0.1
I trusted the certificates: heft trust-dev-cert

Everything as the setup and Hello World webpart documentation describe for Minimal yo template but I am getting the error below as part of the webpart content when it is inserted into a page

Something went wrong
If the problem persists, contact the site administrator and give them the information in Technical Details.

Technical Details
ERROR: [object Object]

Where to go from here? Nothing on the Dev Tools Console, nor network tab.

package.json
SpDemoWebPart.ts.txt

[ololonly]

@mfornaris did you find the reason?

[mfornaris]

No, I have not been able to figure this out. As I mentioned, it is a 101 out the box webpart generation which does not work

[VesaJuvonen]

@ololonly & @mfornaris - there was an issue on this at #10901 which was resolved and fixed. We had an issue on the 1.23.1 version.

When you see any of these kind of issues with SPFx - please submit an issue so that our vendor team can help - and more importantly so that our engineering team is also aware of the issue. This should be now resolved.

[maupatt]

I started a new folder and a fresh install using a clean yo @microsoft/sharepoint and heft start. I don't know what I had done previously but this time it worked like a charm. I guess you can disregard as I probably wouldn't be able to duplicate the problem.

[maupatt]

I have the same experience.

• typescript 5.5.3
• node v22.22.0
• react 17-0-2 - 17.0.2
• @microsoft/generator-sharepoint@1.23.0
• @microsoft/spfx-cli@0.1.0-pre.3
• @rushstack/heft@1.2.19
• gulp-cli@3.1.0
• gulp@5.0.1
• yo@7.0.1
  I see errors:
  error SPFeedback.SPFeedbackUtility.g Cannot read properties of undefined (reading 'getPageBasicInfo')
  error MySiteCache.Page has not yet g
  error ComponentPerfLogger.end Wrong usage: should call start first with scenarioName=ToolboxRender
  error WebPartZone.didMount.load
  When browsing at workbench url https://mytenant.sharepoint.com/_layouts?15/workbench.aspx

[VesaJuvonen]

@maupatt - as the exception is different than with @mfornaris, root cause is different.

Can you please submit an issue in this repo with the requested details. This then enables our vendor team to start building repro - so that our engineering team can provide input and support for you as fast as possible. Thank you 🙏

[VesaJuvonen]

@maupatt - Seems that you've been using SPFx CLI for the scaffolding - which could be relevant, so please be specific on how did you scaffold and create the solution when you submit the details in issue. Thanks for that advance.

[mfornaris]

Hi @VesaJuvonen
I scaffold it very straight forward, nothing fancy

C:\Garbage__>yo @microsoft/sharepoint

 _-----_
|       |    .--------------------------.
|--(o)--|    |      Welcome to the      |

---------´ | SharePoint Client-side | ( _´U_ ) | Solution Generator |
/A\ '--------------------------'
| ~ |
'..'_
´ |° ´ Y

Let's create a new SharePoint solution.
✔ What is your solution name? World
list prompt is deprecated. Use select prompt instead.
✔ Which baseline packages do you want to target for your component(s)? SharePoint Online only (latest)
list prompt is deprecated. Use select prompt instead.
✔ Where do you want to place the files? Use the current folder
Found npm version 11.13.0
✔ Do you want to allow the tenant admin the choice of being able to deploy the solution to all sites immediately without
running any feature deployment or adding apps in sites? No
✔ Will the components in the solution require permissions to access web APIs that are unique and not shared with other c
omponents in the tenant? No
list prompt is deprecated. Use select prompt instead.
✔ Which type of client-side component to create? WebPart
Add new Web part to solution world.
✔ What is your Web part name? World
✔ What is your Web part description? World description
list prompt is deprecated. Use select prompt instead.
✔ Which framework would you like to use? No JavaScript framework

[VesaJuvonen]

@mfornaris Can you please submit these details as an issue, so that we can get our process moving on helping you - with our vendor and engineering resources. Thank you.

if this still is an issue. If not - great.