Closed ganemone closed 6 years ago
hey @ganemone thanks for the report.
I forced a change to the document with npm star
and the new version was replicated to the "corgi" document correctly.
we changed some backends today and i'll track down the root cause.
looks like this is fixed. thanks again for the report.
Seeing an odd issue where the latest version of a published package is failing to install. I have tracked it down to some odd behavior with the registry and the accept header.
The
npm info
command shows the latest version (0.2.1
)Verbose logged npm install shows a failed install due to an
ETARGET
error.If I curl the metadata endpoint directly, and include the accept header included by the npm and yarn clients, I don't see the
0.2.1
version.If you remove the accept header, it returns the
0.2.1
version correctly.