Open jd-carroll opened 3 months ago
I think it needs to be said that this is a little frustrating. I truly appreciate everyone's effort in pulling this tool together and maintaining it, but this is the second pretty significant regression (failure?) I've encountered this year.
And the most frustrating part of all of this is that I don't even want to use Nx. I would like to use Lerna.
In all seriousness, I think you should do one of the following:
1) Delete / Deprecate / Archive the Lerna project to make it clear that it doesn't exist any more.
2) Delete all nx
dependencies from the Lerna project.
Again, I really do appreciate the investment Nrwl is making in the monorepo tooling space and that at the end of the day Nrwl is a business that needs to make money.
So make it clear, is it Nx or Lerna? And if Lerna is still a thing, then it should be independent of Nx.
To reproduce in any project, add a dependency to @yarnpkg/builder
The root cause of the issue appears to be in how they define their esbuild
dependency:
{
"name": "@yarnpkg/builder",
"version": "4.1.1",
"license": "BSD-2-Clause",
"bin": "./lib/cli.js",
"exports": {
".": "./lib/index.js",
"./cli": "./lib/cli.js",
"./package.json": "./package.json"
},
"dependencies": {
"@yarnpkg/cli": "^4.2.1",
"@yarnpkg/core": "^4.0.5",
"@yarnpkg/fslib": "^3.0.2",
"chalk": "^3.0.0",
"clipanion": "^4.0.0-rc.2",
"esbuild": "npm:esbuild-wasm@^0.15.15",
"semver": "^7.1.2",
"tslib": "^2.4.0"
},
Does that make this a @yarnpkg/builder
issue: Maybe
Is this still an nx
issue: Absolutely
Current Behavior
Expected Behavior
lerna run
to workGitHub Repo
No response
Steps to Reproduce
lerna run
(probably with esbuild involved)Nx Report
Failure Logs
No response
Package Manager Version
No response
Operating System
Additional Information
No response