[BUG] `npm` doesn't correctly resolve workspaces when defining a dependency using GitHub URLs about cli HOT 6 OPEN

I am also experiencing this on npm 10.8.2.

from cli.

I believe it's not suppose to work like that, whatever git repo url provided in package.json that will be considered the packages. Based on what I can understand from the write up is that you want npm to recognize that there is a workspace package in git repository and you want to map @org/dep-y of your package.json to internal folder/workspace of git repository package.

I couldn't find any reference of this behaviour in documentation, could you please provide link to it if you are referring in npm doc ?

from cli.

As written at the beginning, if it's not a bug, then it's a limited behaviour in the functionality or the documentation.

The documentation explains how to link a package via GitHub, however if this package is inside a workspace, the documentation doesn't explain how I can do that. If I attempt to do it by following the documentation, an error is thrown.

from cli.

@ematipico As you mentioned Documentation does explain how to use package if that package is GitHub repository, however if a package resides inside a folder/directory within a repository, this behaviour is not supported as far as i know. You can only directly use GitHub repository as mentioned in the documentation.

from cli.

@milaninfy I understand and know that; however, you didn't tell me how to resolve this issue. Is the documentation outdated? Is it a bug in the package's resolution when using a git repository? Is it missing functionality that requires an RFC?

from cli.

Assigning P1 for now, We may need to check few things, However it might not be inline with this bug report but a different bug related to workspaces and git.

from cli.