[Case Study] Is it possible to have nested worktrees?

[zdm]

Hi,
I have following structure.

(1) package.json - workspaces: ["*"]
|--- (2) package.json - workspaces: ["*"]
     |--- (3) package.json

How it is possible to make (3)package.json to be a part of worktree (2)?

Currently when I run yarn from dir (3) it is trying to create .yarn.lock under top-level dir (1).

So, I need to make worktree (2) isolated from worktree (1) but is should be a subdirectory of (1).

I hope, you understand my question. ;-)

[zdm]

In other words:

1. I have two projects;
2. Both are configured as worktrees;
3. Project2 is located in subdirectory of project1;

I need to make project2 worktree to be isolated from project1.

[arcanis]

If I understand correctly there will always be a single lockfile with the current model. We may consider read-only views in the future, but not until the next major at the very least.

[eliw00d]

I am also trying out nested worktrees but the documentation is not very clear on how to do so. I have the following setup:

/package.json (workspaces: ["backend", "frontend"])
/backend/package.json (workspaces: ["services/*"])
/backend/services/**/package.json
/frontend/package.json (workspaces: ["applications/*"])
/frontend/applications/**/package.json

However, when I install from the root the dependencies in services and applications do not get installed.

[merceyz]

This issue is seems to boil down to per workspace lockfiles so closing as a duplicate of #1223 even though this was opened first as that has more details

However, when I install from the root the dependencies in services and applications do not get installed.

@eliw00d That looks correct, could you open a issue with a full reproduction?