-
Notifications
You must be signed in to change notification settings - Fork 1k
Pop up won't go away when using 1.21.1 even though gulp serve is running and everything is working fine: "Your web part will not appear in the toolbox. Please make sure "gulp serve" is running in a web part project." #10245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hello @kbeeveer46, |
@kbeeveer46, https://learn.microsoft.com/en-us/sharepoint/dev/spfx/release-1.21.1 |
I am already on v1.21.1. The issue only appears after upgrading to it. Someone also left a comment in that post that the issue still appears in 1.21.1. The engineering team has not replied with a fix. Here's a screen recording I took after creating a new 1.21.1 project and running it. https://streamable.com/2ynz5g |
We’ll follow up with our engineering team and provide you with the latest status. |
This is a huge blocker for testing the SPFx web part changes, could you please update on the same? |
@pravin-durgam you can use a regular SPFx page for testing (not work bench), on a normal page there are no any issues. You just need to add a query string to the end of the page // ==UserScript==
// @name New Userscript
// @namespace http://tampermonkey.net/
// @version 2025-05-12
// @description try to take over the world!
// @author You
// @match https://<your tenant>.sharepoint.com/*
// @icon https://www.google.com/s2/favicons?sz=64&domain=sharepoint.com
// @grant none
// ==/UserScript==
(function() {
'use strict';
const url = window.location.href;
if(url.indexOf("_layouts/15/workbench.aspx") == -1) return;
const interval = setInterval(function(){
if(document.querySelector("[data-automation-id=GulpServeWarningOkButton]")){
document.querySelector("[data-automation-id=GulpServeWarningOkButton]").click();
clearInterval(interval);
}
}, 50);
})(); If you want to use it, you need to replace |
This issue appears to be fixed now. I assume it was a change on Microsoft's end? |
@kbeeveer46, |
The issue seems to be fixed, It's working great. Thank you Microsoft team for the immediate fix.
This is great workaround, However the fix has been applied by Microsoft now, I can confirm the same today. Thank you for your great help. |
The issue seems to be fixed today, It's working great, Thank you Microsoft team for the immediate fix. |
@kbeeveer46, Thanks in advance! |
Uh oh!
There was an error while loading. Please reload this page.
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
Additional environment details
Node v22.15.0
SPFx v1.21.1
Describe the bug / error
I upgraded to 1.21.1 and everything is working fine. I can build and run my project and all web parts seem to be working fine but this pop up appears on every page load. This also happens when creating a new blank SPFx project from scratch. I just tested it by editing the default web part and refreshing the page.
I'm using the following workbench URL
https://xxxxxx.sharepoint.com/sites/ClientPortalQA/_layouts/15/workbench.aspx?debug=true&noredir=true&debugManifestsFile=https://localhost:4321/temp/build/manifests.js
and when I browse to the manifest file it loads and I can view it
https://localhost:4321/temp/build/manifests.js
The console shows the following error in my custom project (not a new one). Why is it showing the old path in the first few lines but correct path in the last 4?
This is the terminal log after I ran gulp serve on my custom project (not a new one) and added a web part
Steps to reproduce
Create a new project and run it. The pop up will appear when the browser automatically opens by VS Code and after making an edit to the default web part and refreshing the page.
Expected behavior
The pop up should not appear because Gulp Serve is already running
The text was updated successfully, but these errors were encountered: