jsdocs-io / web Goto Github PK

When trying to validate a captcha on local host (docker) with Test Keys (try all of them), the result is always "not-using-dummy-secret" , i.e. "Must use the test secret key when using a test verification token".

Configuration :

HCAPTCHA_VERIFICATION_SERVER=https://hcaptcha.com/siteverify
HCAPTCHA_PUBLIC_KEY=10000000-ffff-ffff-ffff-000000000001DDD
HCAPTCHA_PRIVATE_KEY=0x0000000000000000000000000000000000000000

Request :

https://hcaptcha.com/siteverify?secret=0x00000000000000000000000000000000000000&response=10000000-aaaa-bbbb-cccc-000000000001&remoteip=172.17.1.1

{"success":false,"credit":false,"hostname":"dummy-key-pass","error-codes":["not-using-dummy-secret"],"challenge_ts":"2023-03-07T08:56:34.975Z"}

How can I have a valid capthca on local host through docker ?

Hi, sorry to chime in to ask about this matter,

I love jsDocs.io, it helps me a lot while deeply exploring new packages, however, most "modern"-targeted packages now have moved to .d.mts export only and unfortunately this is not supported yet, how is the progress on this?

Amazing work and wishes you the best!

Please use this issue template to report a package that you know is documented but for which you found missing or incorrect documentation on jsDocs.io.

Note: If the package itself has no documentation in the source code, you will need to contact the author of the package.

Package name: kontroll

Package version: 0.1.2

Problem (check all that apply using an [x]):

• Missing documentation
• Partial documentation
• Incorrect documentation
• Exposed private documentation
• Other

Optionally, briefly describe the problem:
Hi, quoting @velut from #503 (comment),
Please help me enable analysis for the package, thanks!

Please use this issue template to report a package that you know is documented but for which you found missing or incorrect documentation on jsDocs.io.

Note: If the package itself has no documentation in the source code, you will need to contact the author of the package.

Package name: exome

Package version: 2.0.3

Problem:

• Missing documentation
• Partial documentation
• Incorrect documentation
• Exposed private documentation
• Other

Optionally, briefly describe the problem:

It shows Unfortunately type definitions are currently not available for this package

Please use this issue template to report a package that you know is documented but for which you found missing or incorrect documentation on jsDocs.io.

Note: If the package itself has no documentation in the source code, you will need to contact the author of the package.
this issue

and I expect

Package name: name-goes-here

Package version: version-goes-here

Problem (check all that apply using an [x]):

• Missing documentation
• Partial documentation
• Incorrect documentation
• Exposed private documentation
• Other

Optionally, briefly describe the problem:

Please use this issue template to report a package that you know is documented but for which you found missing or incorrect documentation on jsDocs.io.

Note: If the package itself has no documentation in the source code, you will need to contact the author of the package.

Package name: @unocss/core

Package version: 0.56.5

Problem (check all that apply using an [x]):

• Missing documentation
• Partial documentation
• Incorrect documentation
• Exposed private documentation
• Other

Optionally, briefly describe the problem:

https://www.jsdocs.io/package/@unocss/core The page only mentions that "Unfortunately type definitions are currently not available for this package" but doesn't show why or how it could be improved.

Please use this issue template to report a package that you know is documented but for which you found missing or incorrect documentation on jsDocs.io.

Note: If the package itself has no documentation in the source code, you will need to contact the author of the package.

Package name: name-goes-here

Package version: version-goes-here

Problem (check all that apply using an [x]):

• [ X] Missing documentation
• Partial documentation
• Incorrect documentation
• Exposed private documentation
• Other

Optionally, briefly describe the problem:

I always got a 404 error when I clicked on one of the results after searching for a package like React. Please fix this.

Redirects lose the requested page and don't allow the user to retry. The correct solution would be to return a 503 code, perhaps with a custom HTML page (but not necessarily)