| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Constraint: allow-directory governs directory dependencies, not the package explicitly selected for pack or publish. Rejected: Override only in publish | leaves libnpmpack callers and npm pack inconsistent at the same policy boundary. Confidence: high Scope-risk: narrow Directive: Keep registry, remote, file, git, and dependency resolution subject to their configured fetch policies. Tested: node . run test; node . run test -w libnpmpack; publish and pack dry-run smoke for allow-directory=none|root; registry/file denial probes; git diff --check Not-tested: Manual CLI smoke on non-Linux platforms
|
🎉 Backport to release/v11 created: #9916 |
Sorry, something went wrong.
Backport of #9756 to `release/v11`. Co-authored-by: Yashas Gunderia <68075205+ychampion@users.noreply.github.com> Co-authored-by: ychampion <ychampion@users.noreply.github.com>
| Back | FazBrowse Home | New Git URL |
Summary
Why
allow-directory restricts directory dependencies, but the local package selected for packing or publishing is the command target. The current flow applies the dependency policy to that target during manifest or tarball preparation.
Closes #9755.
Validation