Skip to content

docs(samples): note npm CFS proxy for TabApp Web build#600

Open
corinagum wants to merge 1 commit into
mainfrom
cg/npm-registry-docs
Open

docs(samples): note npm CFS proxy for TabApp Web build#600
corinagum wants to merge 1 commit into
mainfrom
cg/npm-registry-docs

Conversation

@corinagum

Copy link
Copy Markdown
Collaborator

What

Adds a note to core/samples/TabApp/README.md under Build & Run.

Why

The TabApp Web frontend (React/Vite) uses npm install, which is blocked on Microsoft-managed devices. The .NET SDK release build is unaffected (NuGet) — this is purely a dev-time sample note.

Notes

  • Links to aka.ms/CFS; external contributors unaffected.
  • No internal feed URL committed.

Copilot AI review requested due to automatic review settings July 10, 2026 21:46

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds an internal-development note to the TabApp sample docs explaining why npm install can fail on Microsoft-managed devices and where to find setup guidance for the Central Feed Services (CFS) proxy.

Changes:

  • Adds a “Microsoft-managed devices” callout under Build & Run in the TabApp sample README.
  • Links to the CFS setup instructions at aka.ms/CFS without committing any internal feed URL.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

The TabApp Web frontend uses npm, which is blocked on Microsoft-managed
devices. Add a note pointing to the CFS proxy setup at aka.ms/CFS.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 75223766-eb7f-4146-9d06-2c4e1e22f42e
@corinagum corinagum force-pushed the cg/npm-registry-docs branch from 0a8bfe6 to 4169877 Compare July 10, 2026 22:23
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

Successfully merging this pull request may close these issues.

2 participants