Unable to publish under same name as public registry packages about npm-register HOT 9 OPEN

My workaround/safeguard (which feels fine) is to only publish scoped packages under namespaces I own on the public registry.

from npm-register.

Thanks for the workaround hack @jtrussell!

It does make the whole thing a bit messy if you want to use npm-register as a public-facing registry for users though.

from npm-register.

This is by design (though maybe there could be better documentation and/or behavior around it). registry.npmjs.org is supposed to be the source of truth with npm-register providing additional packages. @jtrussell mentions the best way around it.

from npm-register.

@dickeyxxx perhaps it would be reasonable for a publish to fail (loudly) if the name in question already exists in the publish registry? I'd be interested in putting a PR together if that sounds reasonable. I'm not sure I'd consider this a breaking change as the "successful" publishes never resulted in usable versions of the package.

from npm-register.

definitely down for that @jtrussell. There is still an outstanding issue of someone later publishing a package, but that's a good first step.

from npm-register.

Haven't forgotten about this but was wondering on a possible solution to the other half of the issue. How about a configurable blacklist of package names/patterns to ignore from the uplink registry? E.g. I could:

• Tell npm-register to ignore 'react' on the uplink registery so that I can publish my own version here.
• Ignore packages matching /^@acme\/.*$/ so I can safely publish under that scope even if someone else grabbed it on the public registry.
• Ignore packages 'lodash' and 'underscore' because e.g. my my company decided our apps shouldn't use them.

from npm-register.

👍 sounds like a good solution

from npm-register.

@jtrussell good solution, I'll look to add this to a roadmap after the UI is done.

from npm-register.

Hey folks, just got bitten by this today.

We've always published our beta versions <1.0.0 on our own private repository and decided to release a 1.0.0 version and also make that available publicly on the official NPM registry.

To my surprise our existing internal builds started failing when they couldn't find the older versions of our scoped package.

Any ideas on how to force it to accept packages? :)

EDIT:

For posterity, we've managed to work around the issue by renaming our package and publishing that to the NPM registry 👍

from npm-register.