[BUG] Invalid name: "@apollo/client/core"

[sresch4b]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Hi,

I'm not sure if it is a "bug" or if I just have a wrong understanding of package names. Anyway, I ask why the package name mentioned should be invalid? It may be unusual, but I wouldn't call it invalid. If I understand the rules of https://docs.npmjs.com/cli/v9/configuring-npm/package-json#name correctly.

My reason for asking is that we want to use a tool (CycloneDX) that uses your code. However, because of the error you threw, it cannot react adequately and break.
CycloneDX/cyclonedx-webpack-plugin#745

Can you shed some light on this?

Expected Behavior

Does not throw an error on package names, which contains more than one slash.

Steps To Reproduce

Find a small example here:
https://github.com/sresch4b/cyclonedx-issue

Run yarn install and yarn build

Environment

• npm: 9.5.0
• Node: 19.7.0
• OS: macOS
• platform: Macbook Pro

[AugustusKling]

It seems the Apollo people create package.json files which are not representing real packages to allow importing their client partially. See the code in https://github.com/apollographql/apollo-client/blob/b214dd1d31cdfe6b5477bb5887a7d9615a302b27/config/prepareDist.js#L64 and the comment in apollographql/apollo-client#6656 (review)

Without looking at this in any detail, I have the impression that it would be cleaner if they'd split up their @apollo/client package and remove the linked code entirely.

Regarding the name property of package.json files I can't really follow why exactly the characters /@\s+% (see readme file) would be forbidden. The NPM docs don't have this exact restriction but they mention name can't contain any non-URL-safe characters in https://docs.npmjs.com/cli/v9/configuring-npm/package-json#name.

[wraithgar]

That is an invalid package name for a package.json. It is a valid require, but those are distinct things, one is asking for a package from a registry (package.json) and one is asking for content installed within node_modules (require).

[sresch4b]

@wraithgar Thx for the clarification