yarnpkg/yarn

Yarn add fails if package url should be fetched using "git config --global url"

Open

#2,614 opened on Feb 2, 2017

View on GitHub
 (9 comments) (12 reactions) (0 assignees)JavaScript (41,514 stars) (2,731 forks)batch import
cat-featuregood first issuehelp wantedtriaged

Description

in a project i work in, the line in package.json of a dependancy is:

"some_package": "bitbucket:some_company/some_package#develop"

in an automated environment the following command runs before npm install:

git config --global url."https://x-token-auth:${access_token}@bitbucket.org/some_company/".insteadOf https://bitbucket.org/some_company/

now when running yarn install --verbose i see that yarn first tries to get git refs from the repository but it has no permissions, and fails with 401:

verbose Request "https://bitbucket.org/some_company/some_package.git" finished with status code 302.
verbose Performing "GET" request to "https://bitbucket.org/some_company/some_package.git/info/refs?service=git-upload-pack".
verbose Request "https://bitbucket.org/some_company/some_package.git/info/refs?service=git-upload-pack" finished with status code 401.
verbose Error: Error connecting to repository. Please, check the url.

maybe in case of 401, the repository should be fetched using GIT.

Contributor guide

Tech stack
javascriptnodejs
Domain
toolingauthentication
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Understanding of yarn's git integrationFamiliarity with git config insteadOf
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate how yarn resolves git dependencies, particularly the code that handles HTTP requests to remote git repositories. The issue suggests that after a 401 response, yarn should fall back to using the git CLI command with the configured URL instead. Look at files like src/package fetcher.js or similar modules where git fetching is implemented. Consider adding logic to detect 401 status and retry using 'git clone' or 'git fetch' with the URL from git config insteadOf rules. The existing comments may provide additional context.
Yarn add fails if package url should be fetched using "git config --global url" · yarnpkg/yarn#2614 | Good First Issue