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
Explicit registry flag feature #599
Conversation
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.
I'd rather this was just force pushed into the old PR branch, but if that is truly unrecoverable, we're almost there!
src/commands/PublishCommand.js
Outdated
@@ -338,14 +338,15 @@ export default class PublishCommand extends Command { | |||
}); | |||
|
|||
this.progressBar.init(this.packagesToPublish.length); | |||
this.npmRegistry = this.getOptions().registry; |
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.
This should be done once, in the initialize method.
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.
Moved to runPreparations() so every command has access to it. I hope it does not count as an overkill :)
Sounds good!
… On Feb 11, 2017, at 11:27, Norbert Csaba Herczeg ***@***.***> wrote:
@noherczeg commented on this pull request.
In src/commands/PublishCommand.js:
> @@ -338,14 +338,15 @@ export default class PublishCommand extends Command {
});
this.progressBar.init(this.packagesToPublish.length);
+ this.npmRegistry = this.getOptions().registry;
Moved to runPreparations() so every command has access to it. I hope it does not count as an overkill :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Once @doug-wade has a chance to review this, we'll be good to go. |
Thanks @evocateur ! :) |
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 @noherczeg!
Looks like the master build failed after this landed. |
ugh. must have collided. I'll hop on it. |
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. |
Corrected version of #563
Again, sorry for messing up the previous PR.