denoland / apiland Goto Github PK

We have abysmial test coverage, we need both unit and integration tests.

The biggest challenge is that we need a way to mock the datastore.

makes it hard to spot actually important logs

The crawler in the deno_manual app helps us collect deno.land/manual records. Unfortunately, Algolia didn't allow us to create another index in the deno_manual app currently on an open source plan.

It turns out a costly affair to set up a crawler for a paid application. For the time being, we need to copy the manual index from the deno_manual application to the deno_land application regularly.

from denoland/deno#18877 (comment)

When I access https://deno.land/x/[email protected]/client-s3/mod.ts from the browser, 404 Not Found is displayed, but when I access it from the CLI, I can get the content normally.

PS C:\Users\ayame> curl https://deno.land/x/[email protected]/client-s3/mod.ts
export * from "./S3Client.ts";
export * from "./S3.ts";
export * from "./commands/AbortMultipartUploadCommand.ts";
export * from "./commands/CompleteMultipartUploadCommand.ts";
export * from "./commands/CopyObjectCommand.ts";
export * from "./commands/CreateBucketCommand.ts";
...

As far as I know, the 3 modules aws_sdk, masto, react_icons are no longer accessible from the browser due to website performance issues. (ref: https://github.com/denoland/apiland/pull/86/files#diff-0f333eea5d2787b19b89ca1e52a1d009170cb0ce2adb68a68c7090678fa41175)

In my opinion, when people see 404 Not found when accessing these modules, it gives them the illusion that they have been removed from deno.land. I wish I could see the message "Document rendering was skipped due to performance issues".

https://deno.land/x/[email protected]/mod.ts
It prompt: The documentation for this module is currently unavailable.
I guess it might be caused by @deno-types

deps.ts:

export { Logger } from 'https://deno.land/x/[email protected]/mod.ts'
// @deno-types="https://deno.land/x/[email protected]/index.d.ts"
export { pack, unpack } from 'https://deno.land/x/[email protected]/index.js'
export { serve } from 'https://deno.land/[email protected]/http/server.ts'

When a new module is released, github sends us a webhook. When we handle the webhook, we need to generate doc nodes, filter them, and send them to Algolia along with module meta data.

Previous iterations of dotland supported having your readme file in .github/ or docs/ (just like GitHub does). apiland only supports READMEs at the project root. We should re-add this feature.

This is how this used to be handled in dotland: https://github.com/denoland/dotland/blob/release-1-13-1/util/registry_utils.ts#L334

deploy logs have this recurring error

BadResource: Bad resource ID
    at Object.respondWith (ext:deno_http/01_http.js:278:15)
    at eventLoopTick (ext:core/01_core.js:182:7)

potentially fixed by moving acorn to use Deno.serve

now we have the possibility to search module by name, I hope you add possibility to search module by by key words in git repo description for example when search for react in /x I expect to see all module related to react even the the name don't contain react

Endpoint GET /v2/modules/<module>/<version> provides information specific to the version. It would be nice to have latest as an alias that points to the latest version of the module.

When I request to https://apiland.deno.dev/v2/modules?limit=100&page=11 it says next page is /v2/modules?limit=100&page=12 but https://apiland.deno.dev/v2/modules?limit=100&page=12 returns 404 Not Found.

How can I get a list of all module names?

Hello.
The last version of the package https://deno.land/x/imagemagick_deno is 0.0.14 in deno.land/x but in the git repository there are two more recent tags (0.0.15 and 0.0.16 that wasn't updated) https://github.com/lumeland/imagemagick-deno/tags

The webhook is configured correctly, and looking to the recent deliveries, everything looks fine:

but these two versions are missing in the deno registry. I've also tried to redelivery a webhook without lucky.

Failed moduleitem assertions shouldnt be happening

Currently for high traffic items, these items require round trips to the db to lookup and for high traffic volumes, we should have a better mechanism.

Only module is mutable, the rest of the these types are immutable, though module only changes when a new module is published (or the metrics are run), so invalidation would need to be considered.

I already upload three versions and still not working:

https://deno.land/x/changelog_formatter

I already created other modules, so I don't know what's going on, the webhooks are working fine.

I just created a new release of my module, Capi. Every time we've published a new version, it's been visible on deno.land/x/capi within a minute or so. 40 minutes has passed and still the new version isn't reflected (https://deno.land/x/capi). I'm concerned there may be an issue.

I'd like the ability to publish a specific commit in a repo instead of having to rely on the webhook and tag the repo.

Essentially I would like to make a request using an OIDC token in a GH Action that specifies:

1. The commit hash.
2. The name of the version being published.

Reason: When the main repo gets tagged, I want to run a GitHub action that builds my library and pushes it to an orphaned "build branch". I'd then like to tell apiland that I want to publish this commit with a specific version.

This snippet

1. Create Tui instance

`​``ts
import { crayon } from "https://deno.land/x/crayon@version/mod.ts";
import { Canvas, Tui } from "https://deno.land/x/tui@version/mod.ts";

const tui = new Tui({
  style: crayon.bgBlack, // Make background black
  refreshRate: 1000 / 60, // Run in 60FPS
});

tui.dispatch(); // Close Tui on CTRL+C
`​``

2. Enable interaction using keyboard and mouse

`​``ts
import { handleInput, handleKeyboardControls, handleMouseControls } from "https://deno.land/x/tui@version/mod.ts";
...

handleInput(tui);
handleMouseControls(tui);
handleKeyboardControls(tui);
`​``

3. Add some components

`​``ts
import { Button } from "https://deno.land/x/tui@version/src/components/mod.ts";
import { Signal, Computed } from "https://deno.land/x/tui@version/mod.ts";

...
`​``

Renders order correctly on github:
https://github.com/Im-Beast/deno_tui

But renders only 1's on /x
https://deno.land/x/[email protected]

When I access https://redocly.github.io/redoc/?url=https://apiland.deno.dev/~/spec, "Something went wrong..." is displayed.

Currently we have modules and deno_modules and that is kinda confusing.

As discussed on the Discord Server.

This would be similar to
https://api.npms.io/v2/search?q=maintainer:ultirequiem

This feature would be really useful for portfolios or community projects.

deploy logs have this recurring error

Http: connection closed while sending response
    at async Object.respondWith (ext:deno_http/01_http.js:278:9)

potentially fixed by moving acorn to use Deno.serve

deploy logs have this recurring error

Http: connection error: broken pipe: broken pipe
    at async HttpConn.nextRequest (ext:deno_http/01_http.js:114:21)
    at async serve (https://deno.land/x/[email protected]/http_server_native.ts:90:34)

potentially fixed by moving acorn to use Deno.serve

The URL https://deno.land/x/[email protected] is returning a 500 error.

• #110
• #111
• #112
• #113
• #114
• #115
• #116

Do we want add support for GitLab and BitBucket in the registry?

/cc @ry

low priority

I don't know how common it is, but for kv_toolbox the current version being reported is 0.0.5 but version 0.0.6 exists. I tried redelivering the GitHub webhook, but it complains that the version already exists, and the version is clearly available when requested directly.

this shouldnt be showing in error logs, but rather normal logs

I want to refer to a file in this module, but no response comes back. It seems to be very slow or hung.

https://deno.land/x/[email protected]/tsx/accessible.tsx

The reason that comes to mind is the very large number of files under this directory. there're 2687 files.

https://deno.land/x/[email protected]/tsx?source

update:

Now the response comes back. Apparently complex modules take longer to cache. This does not appear to be a bug, but will be left as an issue.

Loading and docking some modules takes to long in deploy (like std) and exceeds the CPU limit. This means that things will get lazily loaded, but with the caching of pages, it means that many pages will be cached in the datastore with incomplete information, like module doc summaries.

We need to likely have a batch process that runs as a github action which will "cleanup" any incomplete module loads where CPU time won't get exhausted.

Would be nice to have a warning on third-party modules when it contains broken dependencies (deno info fails)

Need the nav as well as the index (dirs without a default module).

https://apiland.deno.dev/v2/modules/std shows latest version at 0.177.1

Being able to view the response from https://api.deno.land/modules without having to put it through a formatter would be nice.