Skip to content

Local workbench (gulp serve) looks completely broken in 1.21 #2796

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

Closed
nbelyh opened this issue May 3, 2025 · 3 comments
Closed

Local workbench (gulp serve) looks completely broken in 1.21 #2796

nbelyh opened this issue May 3, 2025 · 3 comments

Comments

@nbelyh
Copy link

nbelyh commented May 3, 2025

I cannot debug anything in 1.21👀
The gulp serve just doesn't seem to work.

Steps to reproduce is to follow the "getting started" manual (use node 22):

> npm install gulp-cli yo @microsoft/generator-sharepoint --global
> yo @microsoft/sharepoint
... select "WebPart, name=antyhing, webpart name=HelloWorld (default), language=React
> gulp serve

Build succeeds, but serve does not work (manifest.js is generated, though, as /temp/build/manifest.js)

Image

You get this in the browser log:

Image

This is the console:

Image

Looks like gulp serve does not serve manifest.js file for the local workbench in 1.21

Am I doing something wrong? Is it for everyone or just me?


NOTE: If you follow the same steps with NODE 18 and SPFx 1.20, everything works.


After investigating a bit:
If you copy the generated manifest.js file manually from /temp/build/manifest.js to /temp/manifest.js, then it starts working 😕

Copy link
Contributor

Hi @nbelyh! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.

Best regards, Teams Platform

@nbelyh
Copy link
Author

nbelyh commented May 3, 2025

Wrong repository. Duplicate of SharePoint/sp-dev-docs#10053

@nbelyh nbelyh closed this as not planned Won't fix, can't repro, duplicate, stale May 3, 2025
Copy link
Contributor

Tell us about your experience!

Hi @nbelyh! We have closed this issue in our system, but we would love to hear your feedback. To let us know how we did, simply use one of the following emoji icons: 👍 for resolved, 👎 for unresolved, or ❤️ for a great experience on this message. Please use the link for more detailed feedback.

Best regards,
Teams Platform

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant