Skip to content
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

Publish failed when using 3.1.0 not 3.0.4 #317

Closed
jdziat opened this issue Jan 5, 2019 · 3 comments · Fixed by #356
Closed

Publish failed when using 3.1.0 not 3.0.4 #317

jdziat opened this issue Jan 5, 2019 · 3 comments · Fixed by #356

Comments

@jdziat
Copy link
Contributor

jdziat commented Jan 5, 2019

When using a privately hosted repository and i go to publish using the 3.1.0 version it fails with a 403 response. However using the 3.0.4 works as expected. The below is all that is displayed.

np patch

✖ Response code 403 (Forbidden)
@jdziat
Copy link
Contributor Author

jdziat commented Jan 5, 2019

Fails because of the npm name check module.
Changing the below within cli.js fixed it for me:

--skip-name-check  Skip validating the name check

skipNameCheck: {
      type: 'boolean',
      default: false
    },

  const isAvailable = cli.flags.skipNameCheck ? true : await npmName(pkg.name)

@sindresorhus
Copy link
Owner

How are you hosting it privately? Are you using a scoped package or normal package name?

I would prefer to find a way to resolve this without adding yet another flag.

@jdziat
Copy link
Contributor Author

jdziat commented Jan 10, 2019

Just with a verdaccio instance and it's a normal package name.

sindresorhus pushed a commit that referenced this issue Mar 15, 2019
This fixes the name check when publishing to a private registry by skipping it.

Fixes #350
Fixes #317
Closes #318
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants