Joe Pea
Joe Pea
Apparently it is more complicated that that! I ran `corepack enable`, so `yarn --version` in PowerShell shows the latest version. I missed that the output before the above `NX` error...
This is my first time on Lerna v7 with Yarn. Before this, I was using Lerna 4 with npm. But now that I've upgraded, I don't have `npmClient` set but...
Ok I discovered that, in Windows only, it will not fail on the `yarn` command if I start lerna with yarn. For example, if I have a lerna command in...
^ That commit fixes the issue on the lume project.
In the meantime (if we can't use corepack), it looks like Lerna tries to use the wrong version of Yarn, not the one specified by corepack config in package.json (which...
Aha! I upgraded lerna from 4.0.0 to 7.3.1 in my package.json, and now I can reproduce the issue when I run my scripts locally. I should be able to make...
Ok, I've made a reproduction: ```sh $ git clone [email protected]:lume/lume.git tmp-lume-lerna-fail-test $ cd tmp-lume-lerna-fail-test $ git checkout lerna-issue-3866 $ npm run fresh # this clones git submodules, then runs yarn...
Hmmmm, worth noting that in `package.json` I have ```js "workspaces": [ ".", "apps/*", "packages/!(glas|docsifyjs+docsify)" ], ``` which is the only place in the project that mentions both `glas|docsifyjs+docsify` at the...
This is difficult to debug, `WorkspaceContext` is not JavaScript.
Hmmm, ok, apparently it has to do with _two_ things: - workspaces has `!(glas|docsifyjs+docsify)` - `packages/` folder has both `glas` and `docsifyjs+docsify` In order to make the error go away,...