yarnpkg/yarn

can't resolve merge conflicts with --install.frozen-lockfile in .yarnrc

Open

#5,382 创建于 2018年2月20日

在 GitHub 查看
 (11 评论) (9 反应) (1 负责人)JavaScript (41,514 star) (2,731 fork)batch import
cat-featuregood first issuehelp wantedtriaged

描述

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

What is the current behavior?

If a project has a .yarnrc file that specifies --install.frozen-lockfile true, then you can't take advantage of the automatic merge conflict resolution on yarn install.

What is the expected behavior?

Yarn either provides a way to override the settings in .yarnrc during yarn install (e.g. yarn install --no-frozen-lockfile), or provides a new CLI command to explicitly resolve merge conflict markers (e.g. yarn resolve-merge).

贡献者指南

技术栈
javascriptnodejs
领域
clideveloper experiencetooling
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
basic understanding of yarnknowledge of merge conflicts
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
The issue proposes adding a way to override ` install.frozen lockfile true` from `.yarnrc` during `yarn install`, or a new `yarn resolve merge` command. Review the discussion and linked issues/comments (e.g., #5382) for prior art and maintainer feedback. Since yarn 1.x is frozen, consider if this feature could be implemented in Berry (yarn 2+) or if a workaround exists. Check if any config file parsing changes are needed in `src/cli/commands/install.js` or similar.