lerna publish not response
See original GitHub issueExpected Behavior
This should be published successfully
Current Behavior
No matter whether I press any key, no response。
Possible Solution
Steps to Reproduce (for bugs)
lerna.json
<!-- Please paste your `lerna.json` here -->
{
"packages": [
"packages/*"
],
"version": "1.0.0"
}
lerna-debug.log
<!-- If you have a `lerna-debug.log` available, please paste it here -->
<!-- Otherwise, feel free to delete this <details> block -->
Context
Your Environment
Executable | Version |
---|---|
lerna --version |
3.15.0 |
npm --version |
6.9.0 |
yarn --version |
1.3.2 |
node --version |
9.11.1 |
| OS | MacOS Mojave | 10.14 | | — | — | | NAME | VERSION |
Issue Analytics
- State:
- Created 4 years ago
- Comments:5
Top Results From Across the Web
lerna publish not working in GitHub Actions - Stack Overflow
This message occurs after github actions tries to run the lerna publish command. I've tried dozens of variations of installing Lerna globally ...
Read more >@lerna/publish - npm
Publish packages in the latest commit where the version is not present in the registry ( from-package ). Publish an unversioned "canary" release ......
Read more >lerna/publish/README.md - UNPKG
Any versions not present in the registry will. 39, be published. 40, This is useful when a previous `lerna publish` failed to publish...
Read more >Version and Publish - Lerna
Lerna comes with a version command that allows you to increment your package's version number, commit the changes and tag them accordingly. lerna...
Read more >Automating package publishing in JavaScript projects
This post shows you how to automate package versioning and publishing to the registry, ... For Lerna to know which package to publish...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
thank you
this is related to https://github.com/SBoudrias/Inquirer.js/issues/811 and the release of inquirer to version 6.4.0 (at time of writing, 11 hours ago) so this isn’t a lerna issue per-se. A solution is to add the following snippet to your top-level package.json (if you are using yarn)
I am typing from a phone, if someone could make a PR for https://github.com/lerna/lerna/blob/9a47201f3fdd1df09cfb1922f26329d1dc4c8cc5/core/prompt/package.json#L34 and change
to
that would possibly be a quick fix