(Verdaccio) TypeError: Cannot read property 'old' of undefined

[silverwind]

(Verdaccio) TypeError: Cannot read property 'old' of undefined

[silverwind]

This might be a 404 not found, try:

curl -v -H "Authorization: Bearer <token>" https://npm.inc.sh/@inc%2fgotql

(If you post output of that, make sure to remove the token)

[silverwind]

Try 7.1.0, it might just work.

[silverwind]

Can you post your package.json or list of dependencies where you get the error?

[NetOpWibby]

My apologies for the lateness. My registry is here. I only have one public package on it and the dependencies I'm trying to update are private.

I updated to the latest version of updates and the issue remains.

EDIT: This is one of the packages, but it's also available on npm, publicly.

[silverwind]

Looks like the issue is with authorization (info):

$ curl https://npm.inc.sh/@inc%2fgotql
{
  "error": "authorization required to access package @inc/gotql"
}

Do you store your auth token for that registry in a .npmrc file?

I probably need a module that is able to parse the token out of npm's various config files.

[silverwind]

Try with 6.3.0, it should pick up your auth token with the new --auth option.

[silverwind]

Actually, try 7.0.0, I decided to automatically authorize if a token is present, so it should work without extra arguments.

[NetOpWibby]

Alright, I think we're getting closer. I now get this error:

Error: Not found
    at Promise.all.then.dati (~/node_modules/updates/updates.js:220:14)
    at process.internalTickCallback (internal/process/next_tick.js:77:7)

To answer your previous question, my credentials indeed are in my .npmrc file.

[NetOpWibby]

I'm gonna try to fix this as well.

[NetOpWibby]

I added the below lines into this block: https://github.com/silverwind/updates/blob/master/updates.js#L218

console.log("—————");
console.log(data);
console.log("—————");

I saw two of my modules (@inc/gotql and @inc/logger) and { error: 'Not found' }.

EDIT: Those two modules are available on npm so that must be why they appeared. I have two more modules namespaced under @inc that aren't.

[silverwind]

Just to be clear: you're sourceing all your package from the npm.inc.sh registry, right? You do specify -r https://npm.inc.sh to use that registry?

[NetOpWibby]

Not all my packages, just a couple. Most are from npm proper. I don't specify anything to use the registry, I'll check out the other parameters.

EDIT: Specifying the registry didn't work.

[NetOpWibby]

Response from the cURL:

[REDACTED]

[silverwind]

Okay so we need to find out which packages are pulled from npm.inc.sh and which from registry.npmjs.org. I'm sorry, I have never worked with private packages. How do you specify where to pull which package from? Or does npm find that out automatically based on some data in their registry?

[silverwind]

One guess on how it might work: First npm tries to retrieve the package from the private registry, if it gets a 404 there, it pulls the package from registry.npmjs.org. That would explain your 404.

So I think I need to implement #20 and then implement the fallback on 404.

[NetOpWibby]

It does! Thank you @silverwind!