velut / query-registry Goto Github PK

/.../node_modules/query-registry/dist/query-registry.cjs.development.js:747
  } catch {}
          ^
SyntaxError: Unexpected token {

/usr/share/gcui/node_modules/query-registry/dist/query-registry.cjs.development.js:139
    } catch {}
SyntaxError: Unexpected token {

it should be catch (err) { } as per MDN

eg:
registry = 'http://registry.a.com/npm'
name = 'packageName'
request will filter '/npm' path like 'http://registry.a.com/packageName'

expect：
registry = 'http://registry.a.com/npm'
name = 'packageName'
request like 'http://registry.a.com/npm/packageName'

eg:
git url like https://git.a.com/repo

after normalizeRepository get https://a.com/repo

expect:
get https://git.a.com/repo

Hello!

I am using query-registry version 2.6.0. In my tsconfig.json, I don't have "dom" as one of elements in "library" entry, because my library not aimed to be used in browsers.

Running tsc causes the following errors:

    node_modules/query-registry/dist/utils/errors.d.ts(11,24): error TS2304: Cannot find name 'Response'.
    node_modules/query-registry/dist/utils/errors.d.ts(16,15): error TS2304: Cannot find name 'Response'.

This is because Response is not part of globals in Node as it is in browser.

I can do workaround by creating new .d.ts file with the following content:

// fix-qr.d.ts
declare global {
  // To fix compilation errors with query-registry module
  interface Response {}
}

// To fix error:
// Augmentations for the global scope can only be directly nested in external modules or ambient module declarations.ts(2669)
export {};

So this bug is not blocker. But not particularly nice either.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Hi,

I'm trying to get this library working with NextJS in the browser.
I'm getting an import error:

error - ./pages/index.tsx:2:0
Module not found: Can't resolve 'query-registry'
  1 | import PageLoader from "../components/pageLoader"
> 2 | import { getPackageManifest } from "query-registry";
  3 | 
  4 | export default function Profile() {
  5 | 

https://nextjs.org/docs/messages/module-not-found

Please note that it is usable server side, but on the client side as stated in the readme.md.

Any idea why it doesn't work on the client side?

First of all this is a great package.

I couldn't find a way "To request an abbreviated document with only the fields required to support installation"
https://github.com/npm/registry/blob/master/docs/responses/package-metadata.md

Is that possible?
if not can we add a flag or method?