6 Commits

Author	SHA1	Message	Date
btea	d15c27438d	fix: correct url loss pathname (#9548) ... close #9545	2025-05-15 18:30:19 +02:00
Zoltan Kochan	8a9f3a4835	refactor: rename pref to bare specifier (#9445)	2025-04-20 22:58:08 +02:00
mato533	d6a4ff1892	feat(git-resolver): respect proxy settings when resolving git (#9016) ... close: #6530	2025-01-28 18:48:37 +01:00
Utsav Shah	b10096228c	fix(git-resolver): handle private git repo resolution (#8906) ... * fix(git-resolver): handle private git repo resolution In the case where: 1. No git auth token was specified by the user 2. The package requested to be fetched via https 3. The user does not have SSH access to the repo but has HTTPS access 4. The package was hosted in a private GitHub repo pnpm would fallback to using SSH since it was a "likely private repo" and would fail to resolve the package. Now, rather than only checking if there is an auth token specified, it also checks both: 1. Is the repo private 2. Does the user have access to ls-remote it. And if these conditions are true, it tries to use https anyway. This matches the behavior of npm and Yarn berry. Yarn classic also has this bug, and there's a code comment that alludes to it.	2024-12-27 02:48:59 +01:00
Rex Zeng	b13d2dc1ae	feat: add sub folder support for git url (#7487) ... close #4765 --------- Co-authored-by: Zoltan Kochan <z@kochan.io>	2024-01-24 02:15:02 +01:00
Zoltan Kochan	4ca53b0b50	refactor: group projects in different subdirectories (#5659)	2022-11-20 01:35:22 +02:00