Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Possible NPM Registry publish issue

See original GitHub issue

This issue pertains to the following package(s):

GraphQL Playground - Electron App
GraphQL Playground HTML
GraphQL Playground
GraphQL Playground Express Middleware
GraphQL Playground Hapi Middleware
GraphQL Playground Koa Middleware
GraphQL Playground Lambda Middleware

What OS and OS version are you experiencing the issue(s) on?

macOS Sierra and Linux VM

What version of graphql-playground(-electron/-middleware) are you experiencing the issue(s) on?

@apollographql/graphql-playground-html^1.6.0

What is the expected behavior?

The package installs

What is the actual behavior?

Error response not_found when running through yarnpkg or our internal Artifactory

What steps may we take to reproduce the behavior?

This is all I’m running over here, however we go through Artifactory: yarn add @apollographql/graphql-playground-html
Removing ~/.npmrc, it attempts to hit yarnpkg and that also errors
Specifying registry.npmjs.org in a new ~/.npmrc it hits that server, still errors
Checking registry.npmjs.org directly it looks like the package isn’t aliased or deployed fully:

$ curl -s 'https://registry.npmjs.org/@apollographql/graphql-playground-html' | head -c 100
{"error":"Not found"}%
$ curl -s 'https://registry.npmjs.org/@apollographql%2fgraphql-playground-html' | head -c 100
{"_id":"@apollographql/graphql-playground-html","_rev":"4-db82291198ebf269e1c1d3cfc2116326","name":"%

It would seem the registry norm is to respond to both. I tested on a handful of namespaced packages we use, e.g.

$ curl -s 'https://registry.npmjs.org/@types/node' | head -c 100
{"_id":"@types/node","_rev":"1590-43dd788ac349c6b3d47bea085bc29fc0","name":"@types/node","descriptio%
$ curl -s 'https://registry.npmjs.org/@types%2fnode' | head -c 100
{"_id":"@types/node","_rev":"1590-43dd788ac349c6b3d47bea085bc29fc0","name":"@types/node","descriptio%

Please provide a gif or image of the issue for a quicker response/fix.

Issue Analytics

State:
Created 5 years ago
Reactions:3
Comments:5

Top GitHub Comments

1reaction

digitalgearscommented, Aug 14, 2018

I’m not sure to be honest. My guess would be the latter.

0reactions

huv1kcommented, Oct 19, 2018

This is a fork from Apollo, we don’t have any control about it, but they will in future add back this package to server.

Top Results From Across the Web

npm-publish - npm Docs

The publish will fail if the package name and version combination already exists in the specified registry. Once a package is published with...

Cannot publish npm package from release-it #697 - GitHub

I face a similar issue using a private npm registry. It says ERROR User<username> is not a collaborator for <@scope/package-name> . Adding --npm.skipChecks ......

Package is not publishing to npm (not in the npm registry)

Try npm login . In case of npm publish , sometimes misleading message is shown.

NPM instance level registry - publish and install not possible

Module publishConfig is set to the project repository (publish works fine) · Published via personal access token · Set the registry to instance- ......

How to troubleshoot NPM problems - JFrog

Using curl · NPM Login · NPM Install (Non-scoped) · NPM install (Scoped Packages) · NPM Publish · Dependency Rewrites.