Skip to content

Docs: align packaging and setup articles with Heft (SPFx 1.22)#10962

Open
zainshahbaz786 wants to merge 1 commit into
SharePoint:mainfrom
zainshahbaz786:docs/heft-packaging-and-followups
Open

Docs: align packaging and setup articles with Heft (SPFx 1.22)#10962
zainshahbaz786 wants to merge 1 commit into
SharePoint:mainfrom
zainshahbaz786:docs/heft-packaging-and-followups

Conversation

@zainshahbaz786

@zainshahbaz786 zainshahbaz786 commented Jul 23, 2026

Copy link
Copy Markdown

Category

  • Content fix

Related issues

What's in this Pull Request?

Hi team — I'm helping with the Heft doc refresh from #10545.

This PR updates a few spots that still pointed readers at the old gulp workflow:

  • notes-on-solution-packaging.md — describes the package-solution step as a Heft task (same idea as in the provisioning docs).
  • debug-in-vscode.md — image alt text now matches heft start instead of gulp serve.
  • set-up-your-development-environment.md — hosted workbench note references heft start.

I bumped ms.date on the pages I touched. Happy to split into separate PRs if you prefer one file per change.

— Zain (@zainshahbaz786)

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 86d102b:

✅ Validation status: passed

File Status Preview URL Details
docs/spfx/debug-in-vscode.md ✅Succeeded View
docs/spfx/set-up-your-development-environment.md ✅Succeeded View
docs/spfx/web-parts/basics/notes-on-solution-packaging.md ✅Succeeded View

For more details, please refer to the build report.

@zainshahbaz786
zainshahbaz786 force-pushed the docs/heft-packaging-and-followups branch 2 times, most recently from 65eb4a0 to 48a50ec Compare July 23, 2026 13:49
Align packaging and setup articles with SPFx v1.22 Heft commands so readers are not directed to legacy gulp tasks.
@zainshahbaz786
zainshahbaz786 force-pushed the docs/heft-packaging-and-followups branch from 48a50ec to 3a18604 Compare July 23, 2026 13:49
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 65eb4a0:

✅ Validation status: passed

File Status Preview URL Details
docs/spfx/debug-in-vscode.md ✅Succeeded View
docs/spfx/set-up-your-development-environment.md ✅Succeeded View
docs/spfx/web-parts/basics/notes-on-solution-packaging.md ✅Succeeded View

For more details, please refer to the build report.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 48a50ec:

✅ Validation status: passed

File Status Preview URL Details
docs/spfx/debug-in-vscode.md ✅Succeeded View
docs/spfx/set-up-your-development-environment.md ✅Succeeded View
docs/spfx/web-parts/basics/notes-on-solution-packaging.md ✅Succeeded View

For more details, please refer to the build report.

@zainshahbaz786

Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree

1 similar comment
@zainshahbaz786

Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree

@zainshahbaz786

Copy link
Copy Markdown
Author

Small doc-only update for the Heft migration — three spots that still pointed readers at the old gulp flow. Build and CLA are green on my side.

Happy to split into separate PRs or adjust wording if that’s easier for review. Thanks for maintaining this tracker.

— Zain

@zainshahbaz786

Copy link
Copy Markdown
Author

Hi,
its a small doc-only update for the Heft migration, three spots that still pointed readers at the old gulp flow. Build and CLA are green on my side.

Happy to split into separate PRs or adjust wording if that’s easier for review. Thanks for maintaining this tracker.
Regards
Zain

@andrewconnell andrewconnell self-assigned this Jul 24, 2026
@andrewconnell andrewconnell added the pr:in-review Actively reviewing pull request label Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr:in-review Actively reviewing pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants