-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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.
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
Highlight private packages in updated/publish output #436
Conversation
the error in appveyor looks like a problem with the build-cache 😢 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for making these all consistent @chrishelgert!
I've kicked off a re-run in AppVeyor. IMO this is ready to go once that finishes.
@@ -231,7 +232,8 @@ export default class PublishCommand extends Command { | |||
this.logger.newLine(); | |||
this.logger.info("Changes:"); | |||
this.logger.info(this.updates.map((update) => { | |||
return `- ${update.package.name}: ${update.package.version} => ${this.updatesVersions[update.package.name]}`; | |||
const pkg = update.package; | |||
return `- ${pkg.name}: ${pkg.version} => ${this.updatesVersions[pkg.name]}${pkg.isPrivate() ? ` (${chalk.red("private")})` : ""}`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, sees nicer to have it at the end like this. 👍
my pleasure 😃 |
Heh, well... AppVeyor passed, but it looks like this has a conflict with #386 which just merged before it. @chrishelgert Please rebase when you get a chance and we'll get this in! |
@gigabo so no conflicts with base branch :) |
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. |
As requested in #431, this PR adds the styled private annotations for updated and publish-command.
i wasn´t really sure about the position of private in the publish-command, but i think, this solution looks a litte bit nicer.
If you like it otherway, i can change the position :)