yarnpkg/yarn

feature: workspaces: ability to install in a workspace in isolation

Open

#4,099 建立於 2017年8月4日

在 GitHub 查看
 (20 留言) (113 反應) (0 負責人)JavaScript (41,514 star) (2,731 fork)batch import
cat-featurehelp wantedhigh-priorityneeds-discussiontriaged

描述

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

What is the current behavior?

Running yarn install anywhere in a workspaced project will install node_modules in the root with hoisting and symlinking.

But sometimes one needs to test a single workspace installation in isolation from other workspaces.

Example:

I want to check if jest/packages/jest-haste-map has all dependencies listed correctly and I want to install all required node_modules inside jest/packages/jest-haste-map/node_modules.

Solution:

Introduce a new installation flag --ignore-workspaces, when you run yarn install --ignore-workspaces Yarn would not go up the folder tree and will not find the workspace root and will treet the current CWD as a single project.

Questions:

  1. Should we go completely e2e here or still symlink other workspaces if they are in dependencies?

  2. Should we remove node_modules from the root so that it does not affect Node.js module resolution?

貢獻者指南

技術棧
javascriptnodejs
領域
clideveloper experience
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
Understanding Yarn workspacesNode.js module resolutionYarn CLI internals
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
20
研究方向
Investigate how Yarn workspaces currently handle hoisting and symlinking in the v1 codebase, focusing on the install command logic. The issue raises two questions: whether to symlink other workspaces when using ignore workspaces, and whether to remove root node modules. Review the issue comments for additional context. Note that the v1 repository is frozen, so implementation may need to be directed to Yarn Berry.