React Content Query Online - Throws error on loading web part

[maj-jacob]

Disclaimer

Yes

Sample

https://github.com/pnp/sp-dev-fx-webparts/tree/main/samples/react-content-query-online

Contributor(s)

@PopWarner @PaoloPia @hugoabernier

What happened?

The web part does not work after put on page. It throws an "Something went wrong" error. Details only say [object Object]

Maybe relevant: the build throws a warning:

(it's not a CDN issue as in other report suggested)

Steps to reproduce

1. Build webpart
2. Add webpart to page

Expected behavior

a working webpart, without an error

Target SharePoint environment

SharePoint Online

Developer environment

Windows

Browsers

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

What version of Node.js is currently installed on your workstation?

v18.19.0

What version of Node.js is required by the sample?

Node.js v16 | v18

Paste the results of SPFx doctor

√ SharePoint Framework v1.18.2
√ Node v18.19.0
√ yo v5.0.0
√ gulp-cli v2.3.0
√ bundled typescript used
[
{
"check": "SharePoint Framework",
"passed": true,
"version": "1.18.2",
"message": "SharePoint Framework v1.18.2 valid."
},
{
"check": "SharePoint Framework",
"passed": true,
"version": "1.18.2",
"message": "SharePoint Framework v1.18.2"
},
{
"check": "Node",
"passed": true,
"message": "Node v18.19.0",
"version": "18.19.0"
},
{
"check": "yo",
"passed": true,
"message": "yo v5.0.0",
"version": "5.0.0"
},
{
"check": "gulp-cli",
"passed": true,
"message": "gulp-cli v2.3.0",
"version": "2.3.0"
},
{
"check": "typescript",
"passed": true,
"message": "bundled typescript used"
}
]

Additional environment details

No response

[mauricework]

We are getting the same thing here as well. I have been trying for couple of weeks to figure out what I was doing wrong since I am new to this lol.

[aliiamar]

We are getting the same thing here as well. I have been trying for couple of weeks to figure out what I was doing wrong since I am new to this lol.

@mauricework is the issue still persists in your environment? Do share any workarounds if you have :)

[mauricework]

@aliiamar nope it is still a problem.

[johndiehlwh]

Same issue here... did you find a solution yet?

[mauricework]

Same issue here... did you find a solution yet?

Sorry no I have not. I have not had a lot of time to look at it.

[raytri]

I am having this exact problem as well. Would really appreciate an answer, as we are trying to replace an older version of the webpart for security reasons.