+1, this would be great. publishConfig is an important safety measure that npm respects, and it would be potentially very disastrous to run yarn publish in a previously npm-managed package, and accidentally make a private package irrevocably public.

@ljharb I think there are currently measures to prevent that, yarn seems to pick up the private variable, so those would get shortcut, IF you have that set.

Correct, but that's a big "if". Often publishConfig is the only mechanism - and that was sufficient with npm.

Considering that this feature is already in npm I agree, this should be implemented in Yarn.
FYI, we are planning to work big on publish command in the next 3-4 months to bring some lerna features

@bestander this would be cool to add in the short term, I think it would be very useful for users using a private registry. I've got a branch where I'm working on the implementation, pending approval over here.

Nice! I didn't know about publishConfig. I agree with this 😃

This is somewhat related to yarnpkg/yarn#547, where I mentioned that we should have better handling for custom npm servers.

@DarthHater, looks like no one objects and this seems like a very important feature.
Please send the PR when you have a chance :)