Comments (7)
Hi @toddmoorega. I ran into that error this week. Turns out there's a fix in master that just hasn't been published yet.
My workaround was to just use master
instead of v1.1.0
for now.
from lerna.
Maybe i'l just publish 1.1.1 (without uploading git tags to the repo or anythin) with that fix since we want to be using 2.0.
Although you can use the prerelease tag too. { latest: '1.1.0', prerelease: '2.0.0-dev.05e9f0a' }
or master.
Or pin to the git sha of the fix 204b94cea287daba9cb8f0b8c1122072d7df3000
from lerna.
Thanks, I suppose I should of tried that but it was getting late ;)
The master
branch of lerna
works fine, it's publishing like a boss again.
from lerna.
FYI, We published 1.1.1
from lerna.
👍
from lerna.
I guess this can be closed then?
from lerna.
This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs.
from lerna.
Related Issues (20)
- Missing Dependancy when creating a react app in packages folder.
- in lerna independent mode, when i change one package, but lerna will update all packages, why?? HOT 1
- `lerna list` output is truncated at 8192 bytes when `exec`ed HOT 2
- Encountering No changed packages to publish After Upgrading Lerna and Switching to Independent Versioning HOT 5
- Package.json workspaces field is being ignored HOT 1
- No GitHub release is created when using a 'tag-version-separator' other than '@' HOT 3
- Can Lerna Update Only the Version in package.json Without Code Changes? HOT 4
- lerna publish: issuing a WARN for private packages do not make sense
- Running `lerna publish` on Github updates `pnpm-lock.yaml` quotes
- Breaking change added to the footer but still minor version release
- lerna success found 0 packages HOT 2
- CVE-2024-28863 - Lerna using a vulnerable version of `tar` HOT 4
- Cannot spot the changed packages correctly when a custom version provided as command parameter
- lerna version --conventional-graduate does not generate correct changelog HOT 3
- Lerna v8.1.2 uses old version of npm-registry-fetch causing vulnerabilities HOT 1
- Lerna doesn't honor `--yes` option
- tar dependency is broken after `npm audit fix` HOT 1
- Lerna creates identical cache records for different cache hashes
- `npx lerna` fails to run with `undefined` error HOT 1
- run build cannot find package when "packages" is in the path HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lerna.