Library is not compatible with Node 8.9.3 about query-registry HOT 6 CLOSED

Hi @utillity, thanks for opening the issue.

On MDN, it says that the exception part can be omitted (see also their example):

exceptionVar Optional
An optional identifier to hold the caught exception for the associated catch block. If the catch block does not utilize the exception's value, you can omit the exceptionVar and its surrounding parentheses, as catch {...}.

The optional catch binding should be well supported by vendors and tools (see compatibility data).

Can you share some details about how you are getting the error (tools, Node or browser version, commands used) ?

from query-registry.

Hi, I am using this library with node 8.9.3 on an embedded device (unfortunately I can't install a newer node version there). if you want to make it backward-compatible that would be great :)

I'm just using getPackageManifest({ name: packageName, registry: registry }) from your library

from query-registry.

uff, looks like there are a couple of issues blocking me from using your library with node 8.9.3 - don't need to fix the catch :)

from query-registry.

That's unfortunate, what are the other issues if you don't mind? Maybe you could try compiling (part of) the library for your use case or use something like patch-package in your install step.

If you want to implement something yourself to fetch manifests from npm the endpoints look like this https://registry.npmjs.org/<bare name or scoped name>/<version or tag>, for example https://registry.npmjs.org/query-registry/2.6.0 or https://registry.npmjs.org/@types/node/latest.

from query-registry.

this old nodejs version also doesn't support Object.fromEntries. I could pull and try to get everything working, if you need it. I found a simple workaround which works for me - I just use fetch() to get the JSON directly from my private repository, so no dependencies needed :)

from query-registry.

I see. Don't worry about the PR, supporting older versions is not a priority right now and I plan to use features available in current and future releases anyway (like native fetch).

I'm glad you found a solution that works for you.

from query-registry.