Deno has deno.land/x/ already about denopkg.com HOT 8 CLOSED

@egoist True in a way. Ryan's idea is that we should keep Deno core small, so we are moving code that does not quite rely on bindings to deno_std, which is hosted at deno.land/x/std

I'll double check with Ryan about this tho.

from denopkg.com.

Get it, looking forward to a better official solution of using third-party libs 👌🏻

I'm only creating this project to make URLs shorter 😄

from denopkg.com.

Deno is supposed to be a distributed module system, so I welcome more module servers : )
(Ideally github would just have sane URLs to raw content...)

from denopkg.com.

Thanks, but seems deno.land/x is only for a limit set of repos: https://github.com/denoland/registry/blob/master/x/src/database.json

from denopkg.com.

Yes, that's right. There is a note on the https://deno.land/x/ webpage that says

To add a package send a pull request to https://github.com/denoland/registry/blob/master/x/database.json

But I actually am not sure if that means that it is something that they plan to use for the public or if it is just something for their internal stuff so I'll close this out

from denopkg.com.

@kevinkassimo: About registry, there is the deno.land/x/ for redirection of scripts hosted elsewhere, but they are specifically for modules written solely for deno and is similar to golang.org/x/

So I think it is for their internal use.

from denopkg.com.

Hey. deno.land/x is intended for public use. The intention of my comment was to clarify that deno.land/x is not likely to host ported node packages (as asked in that issue).

Though, Ryan never said that there should only be a single “official” registry

from denopkg.com.

@kevinkassimo that's also what I mean, I assume that those packages are part of the GoDeno Project but outside the main GoDeno tree.

from denopkg.com.