yarnpkg/yarn

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

Open

#2.614 geöffnet am 2. Feb. 2017

Auf GitHub ansehen
 (9 Kommentare) (12 Reaktionen) (0 zugewiesene Personen)JavaScript (41.514 Stars) (2.731 Forks)batch import
cat-featuregood first issuehelp wantedtriaged

Beschreibung

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
SchwierigkeitGeschätzte Implementierungsschwierigkeit für neue Contributors, von 1 für sehr kleine Änderungen bis 5 für Expertenarbeit.
3
Geschätzte ZeitEin grober Zeitrahmen, um zu recherchieren, zu implementieren, zu testen und einen Pull Request vorzubereiten.
half day
AktivitätsstatusWie verfügbar das Issue gerade wirkt: frisch, aktiv, stale, blockiert oder wartet auf Maintainer-Input.
stale
KlarheitWie klar das Issue die erwartete Änderung, Akzeptanzkriterien und den nächsten Schritt erklärt.
mostly clear
Voraussetzungen
Understanding of yarn's git integrationFamiliarity with git config insteadOf
EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.
40
Research-Richtung
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.