GPR/NPM Abbreviated metadata responses do not contain peerDependenciesMeta

[tsangste]

Select Topic Area

Product Feedback

Body

Hi, my organisation is starting to use Github Packages to store our private npm packages.

For one of my packages I am using peerDependenciesMeta within the packages.json to set a package to be optional e.g.

{
  "name": "@org/package-b",
  "version": "1.0.0",
  "description": "",
  "peerDependencies": {
    "@org/package-a": "^1.0.0",
  },
  "peerDependenciesMeta": {
    "@org/package-a": {
      "optional": true
    }
  },
}

When doing an npm install it seems that the peerDependenciesMeta is being omitted and installing the optional package which I do not want. After investigating around I found the follow issue for JFrog's Artifactory - https://jfrog.atlassian.net/browse/RTFACT-27265 which looks like the same issue. As stated in the ticket peerDependenciesMeta does not appear in the official Abbreviated metadata format but it is being returned from registry.npmjs.org.

Current workarounds:

1. Host the package within NPM registry (breaks the ecosystem having some packages in npm and some in github packages)
2. Set the peerDependecy package as a devDependency (not ideal but as an internal package best way to have it within github packages)

[tsangste]

Duplicate of https://github.com/orgs/community/discussions/51104