Fix SharePoint Web Part Showing the HelloWorld Interface in Local Workbench
Question details
The user needs to understand why a SharePoint accordion web part built with jQuery UI renders the default HelloWorld web part interface in the local workbench when running gulp serve.

- Product
- Microsoft SharePoint Framework (SPFx) custom web part
- Device & OS
- not provided
- Scenario
- The user is developing a custom SharePoint accordion web part and testing it locally with gulp serve.
- Observed behavior
- The web part renders as the default HelloWorld interface instead of the custom jQuery UI accordion.
Before troubleshooting, confirm that gulp serve is running in the correct project directory and that the local workbench has not cached an older web part build.
Verify the SPFx web part manifest and custom render method
Use this first to confirm the local workbench is loading your custom accordion web part instead of the default HelloWorld output.
A custom SharePoint Framework web part falls back to the default HelloWorld interface when the web part ID or render output does not match the project. Checking the manifest and render method isolates the most common code-level causes.
In the terminal where gulp serve is running, press Ctrl+C to stop the local workbench server.
In Visual Studio Code or your code editor, open the .manifest.json file under src/webparts/yourWebPart and confirm the id and alias match the web part selected in the workbench.
Open the main .ts file for the web part and make sure the render method returns your jQuery UI accordion container HTML instead of the default HelloWorld div.
Run gulp clean, gulp build, and gulp serve in the terminal, then reload the local workbench and re-add the web part.

Ask SharePoint development specialists to review the web part code
Use this when local manifest and render checks do not resolve the HelloWorld output.
Use WPS Office for daily document tasks while you resolve SharePoint web part issues
WPS Office is a free, lightweight Microsoft Office alternative that keeps document tasks moving while you resolve SharePoint web part issues. It opens, edits, and saves Office files with familiar ribbon tools, strong format compatibility, and a smooth migration from Microsoft Office workflows.
- 1. Download WPS Office: Go to the WPS Office download page and click Download WPS Office Free.
- 2. Install and launch WPS Office: Run the installer, open WPS Office, and sign in or continue with the free plan.
- 3. Open Office documents: Open existing .docx, .xlsx, or .pptx files from the WPS Office home screen or File menu.

Frequently Asked Questions
Why does my custom SharePoint accordion web part show the HelloWorld interface?
The local workbench usually loads the default HelloWorld web part when the web part ID in the manifest does not match the selected web part or the render method is returning the default HTML instead of your jQuery UI accordion markup.
How can I check which web part is being rendered in the local workbench?
Open the browser developer console and the SharePoint local workbench details panel, then compare the web part ID and alias shown there with the id and alias in the web part .manifest.json file.
What code should I include when asking for SharePoint web part help?
Include the web part manifest, the main render method, the package-solution.json if relevant, and any gulp serve terminal errors or warnings. This helps specialists review the code-level issue.
Can clearing the local workbench cache fix the HelloWorld web part issue?
Yes, sometimes. Stop gulp serve, delete the local workbench cache or use a private browser window, then run gulp clean, gulp build, and gulp serve again to reload the latest web part build.
Does WPS Office fix a SharePoint web part rendering issue?
No, WPS Office does not develop or fix SharePoint Framework web parts. It is a free Microsoft Office alternative for opening and editing Office documents while you handle SharePoint development separately.




