Skip to content

Question: How can I publish only one package? #1691

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
Gcaufy opened this issue Sep 19, 2018 · 6 comments
Closed

Question: How can I publish only one package? #1691

Gcaufy opened this issue Sep 19, 2018 · 6 comments

Comments

@Gcaufy
Copy link

Gcaufy commented Sep 19, 2018

How can I publish only one package?

If I have 5 packages, and all those 5 packages are changed. They are independent, and I just want to publish one of them, because the others they are not ready yet.

Possible Solution

Can we simply add a Ignore option when doing leran publish?

$ lerna publish
>   Patch (x.x.x)
    Minor (x.x.x)
    .....
    Ignore

Your Environment

Executable Version
lerna --version 3.4.0
npm --version 6.0.1
node --version 8.9.4
OS Version
macOS Sierra ---
@jimmytb
Copy link

jimmytb commented Sep 20, 2018

I believe you can't, you have to do it manually by going to the folder and run:

npm publish

Than manually update the version of the package in the other packages.

This is the way i do it. Hope there is an other way

@Gcaufy
Copy link
Author

Gcaufy commented Sep 20, 2018

@jimmytb yup, this is what I am doing right now. I hope lerna can support publish one single package. then you don't care about the package.json and the git tag and git commits .

@evocateur
Copy link
Member

You can't. A Lerna-managed monorepo doesn't work that way.

@Gcaufy
Copy link
Author

Gcaufy commented Oct 2, 2018

@evocateur any reason why not to support it?

@evocateur
Copy link
Member

Because it breaks the fundamental mechanism Lerna uses to determine which packages need to be published? Absolutely nothing stopping you from not placing several packages in the same monorepo that apparently shouldn't be.

@Gcaufy Gcaufy mentioned this issue Oct 2, 2018
Closed
9 tasks
@lock
Copy link

lock bot commented Dec 27, 2018

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.

@lock lock bot locked as resolved and limited conversation to collaborators Dec 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@evocateur @Gcaufy @jimmytb