[Daniel Castro (castrodd)]

Summary

Re-enables the npm packaging and publishing reverted in #5740 and #5742. The earlier attempt failed because npm ci fetched dependencies from the registry (EPERM on registry.npmjs.org/yauzl), which network isolation blocks.

Changes

• New pack-npm.ps1 builds the tarballs without any registry access.
• Package name and version are set in package.json and npm-shrinkwrap.json, and the locked dependency graph is kept unchanged. Dependencies aren't bundled, and the prepack hook uses only Node built-ins. Consumers install the locked dependencies normally.
• Restores azure-functions-core-tools and azure-functions-cli in the CLI release pipeline. This re-enables the npm artifact, staging, and the publish stage. Manual release approval is unchanged.
• Adds a local regression test, test/Installers/NpmPackaging.test.js. It checks for no registry requests, correct package identity and contents, and that failures fail the build. It is not run in the pipeline.
• Adds an npm packaging section to docs/repo-structure.md.

Validation

• The local test passed 4/4 on Windows (Node 25, npm 11) and on Linux (Node 22.23.4, npm 10.9.9).
• It found and fixed a registry call from npm's update notifier on Linux.
• The pipeline has not been run on this change yet.

[Copilot]

🟡 Changes recommended

The npm installer's expected archive names and formats do not match the staged release assets.

1 open issue

• Fix npm installer asset names and archive format mismatch · New

What changed in this PR

Restores npm packaging and publication for both CLI package names, replacing dependency restoration with offline tarball creation to support network-isolated builds.

Changes:

• Adds an offline packaging script that updates package identity while preserving locked dependencies.
• Re-enables npm artifacts, staging, and publication without changing manual release approval.
• Adds local regression tests for registry isolation, package contents, and failure handling.

File	Description
test/​Installers/​NpmPackaging.test.js	Adds offline packaging and failure-path tests.
eng/​scripts/​pack-npm.ps1	Creates both npm packages without registry access.
eng/​ci/​templates/​jobs/​build.yml	Invokes the offline packaging script.
eng/​ci/​release/​official-release.cli.yml	Restores npm artifact staging and publication.

_{Review effort: Balanced}

[Francisco Gamino (Francisco-Gamino)]

Looks good overall. I did not find any blocking issues with the implementation.

Non-blocking: the new NpmPackaging.test.js regression suite is not currently part of the automated CI path. It would be good to wire this suite into CI so the release-packaging regression remains covered.

The implementation itself looks good to me.