yarnpkg/yarn

Yarn resolutions only works with fixed versions not dist-tags

Open

#6.666 geöffnet am 12. Nov. 2018

Auf GitHub ansehen
 (3 Kommentare) (6 Reaktionen) (1 zugewiesene Person)JavaScript (41.514 Stars) (2.731 Forks)batch import
cat-featurehelp wanted

Beschreibung

Do you want to request a feature or report a bug? bug

Yarn resolutions only works with fixed versions, not dist-tags

What is the current behavior? Yarn installs react@latest not react@next

If the current behavior is a bug, please provide the steps to reproduce. run the yarn install on the following package.json document

{ "name": "yarn-test", "version": "1.0.0", "license": "ISC", "private": true, "resolutions": { "react": "next" }, "dependencies": { "react": "latest" } }

What is the expected behavior? Yarn installs react@next not react@latest

Please mention your node.js, yarn and operating system version. yarn: 1.12.3 node: 8.11.4 os: Windows 10

Contributor Guide

Tech Stack
javascriptnodejs
Domain
tooling
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.
over 1 week
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.
clear
Voraussetzungen
understanding of yarn resolutionsnpm dist tagsyarn package resolution logic
EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.
15
Research-Richtung
This issue is from the frozen Yarn v1 repository. The bug is that resolutions only work with fixed versions, not dist tags like 'next' or 'latest'. The expected behavior is to resolve the dist tag to a specific version. First, confirm if this bug has been addressed in the Yarn Berry (v2+) repository. If not, the fix likely involves modifying the resolution logic in the Yarn codebase, possibly in the 'resolutions' handling code within 'src/package resolver.js' or similar. Look at how Yarn currently resolves dist tags in dependency resolution and compare with how it handles them in resolutions. The issue has an assignee but no linked PR, so it may be unclaimed for a first time contributor, but given the frozen status, it's better to focus on Berry.