yarnpkg/yarn

Private npm registry authentication issue on yarn.lock and package.json semver mismatch

Open

#5,256 创建于 2018年1月20日

在 GitHub 查看
 (3 评论) (0 反应) (1 负责人)JavaScript (41,514 star) (2,731 fork)batch import
good first issuehelp wantedtriaged

描述

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

What is the current behavior? Yarn does not authenticate with the private npm registry when the package.json and yarn.lock have a semver mismatch for a spesific package.

For example: yarn add css-hot-loader edit package.json and remove the carrot (^) from the version yarn install Result: Rejected 401, Unauthenticated

OS: Linux, Ubuntu (Heroku)

贡献者指南

技术栈
javascriptnodejs
领域
clideveloper experience
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
Familiarity with npm registries and authenticationUnderstanding of semver range resolution
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
20
研究方向
Investigate the authentication flow in Yarn's resolver when resolving packages from a private registry. Focus on the interplay between package.json version ranges and yarn.lock locked versions. Look at relevant files such as src/resolvers/index.js and src/util/request manager.js. Check the issue comments for any prior investigation or maintainer notes.