If you visit this page: https://deno.land/x/date_fns/addMonths/index.js you'll see a 404 error.

This reporter seemed to think it was an issue with JS files: https://github.com/denoland/registry/issues/177

However, if you look at the "repository" link on the index.js page linked above, you'll see it points to: https://github.com/date-fns/date-fns/tree/mastersrc/addMonths/index.js

Note /tree/mastersrc/, which should actually be /tree/master/src/. I suspect this might have something to do with the handling of the path parameter in database.json: https://github.com/denoland/deno_website2/blob/92a20e81c51c051080311c2edefe517049dbafcd/src/database.json#L116

Note the old registry code has a leading /: https://github.com/denoland/registry/blob/714ffcf29d55620fb02b53c99c7d954a366a19e7/src/database.json#L116

Hi,
In the registry page the top menu (Documentation, Repository, Raw) are displayed with BR and takes extra vertical spaces especially in mobile view.

I want to change this menu to inline horizontal view:

Documentation | Repository | Raw

Please let me know if you agree with this minor change to PR.

Thanks

@lucacasonato

https://dash.cloudflare.com/?account=workers/plans
https://developers.cloudflare.com/workers/about/limits/#number-of-requests-limit

We should probably support viewing images in the registry rather than just showing weird chars in code blocks.

example: https://deno.land/std/log/logger.ts should have a link to https://github.com/denoland/deno/blob/master/std/log/logger.ts

Also for markdown pages.

Also support branches properly.

Benchmarks: https://deno.land/benchmarks

• Broken link: https://github.com/denoland/deno/blob/master/tools/hyper_hello.rs
• This happens because hyper_hello was moved to it's own crate in denoland/deno#2641

We should add darkmode again like we had on the v1 site. It should be based on prefers-color-scheme again.

We have to update:

• main layout (material-ui theme)
• code blocks (so cant use github-gist theme anymore)
• charts (once/if #39 is merged the apexcharts theme)
• invert deno logos

@ry, The prettier HTML code is being shown between markdown. I was also trying to make the toc but its not being rendered properly. Please guide how to solve this. Would like to work on it. Thanks.

This screenshot is from the Manual page.

The main page API Documentation links to a non-existent page: https://deno.land/typedoc/

Problem

Shell commands on https://deno.land/#install aren't rendered as code.

1. This overflows on mobile allowing to scroll on the y-axis
2. It's inconsistent with other pages like https://deno.land/std/manual.md#setup

Solution

Modify the install and example commands in Home.js to use <CodeBlock/>

Not sure if this is the right place for this, but here goes.

First time visit to deno.land (no prior visits) serves up the http version rather than https. Not sure if I'm missing something but I assume redirecting to https is preferable.

To repeat this behavior, cookies should be cleared (obviously) and visit http version or just type deno.land

Just thought I'd let you know.

Watching the project with interest.

Clicking the "master branch" link in the Benchmarks page treats the link as a route: https://deno.land/https://github.com/denoland/deno.

I think this should be an href instead.
https://github.com/denoland/deno_website2/blob/d0b37acea76c2f80866d99a4d89859b7bc26981a/src/Benchmarks.tsx#L124

take for example the green...

Same as #78.

Related to #70, #104

Allow selecting lines with URL fragment: http://deno.land/std/http/server.ts#L1-#L5

@j-f1 implemented this already somewhere in https://github.com/denoland/registry/tree/master/src so maybe try to reuse code from there.

Currently it is possible to inject javascript into pages that render markdown using, for example, a <img> element. This element has an onload parameter that will execute any JS that is passed to it once is succeeds/fails in loading the image.

Instead of blacklisting tags like we do now - currently only <script> is blacklisted - we should whitelist 'known good' tags like comments and <div>. The whitelist Github uses is more complex and is 'documented' here. It also takes the actual params of the tags into account.

We should only display the documentation button on supported formats.

If you check latest benchmarks (https://github.com/denoland/deno/runs/274208380) you can see that both of those charts should be <2s but all of the results are >4s on charts.

CC @lucacasonato @ry

https://deno.land/docs?url=https://unpkg.com/browse/[email protected]/chain/chain.js

This should simply reuse src/Docs.tsx

Go to https://deno.land/x/std/http/file_server.ts?doc

Page is empty, because there are no docstrings in that file. It would be nice if Documentation button was hidden if there are no docstrings.

The top page's title is now deno /. This doesn't look ideal. This also affects the title in the google search result page.

This is difficult to read

I would prefer we keep the UI very minimal... these buttons do not seem so minimal. Links would be fine - at least they wrap.

https://deno.land/x/deno/cli/js/lib.deno_runtime.d.ts?doc

related: denolib/setup-deno#11
Using Github API will limit the rate.

depends on #43

set it up here https://github.com/denoland/deno_website2/blob/fbe617646c93dfff919d4d70722be82e5527e3f0/.github/workflows/build.yml#L16
and no need to add comprehensive tests, just add an example of how to test react (a good example test would be to check that the home page renders properly and contains the word "Deno")

Hi Ryan,

Can i help you with site?

I have a lot experience work with React and i have a free time.

example: https://deno.land/x/abc/dev_deps.ts

Statements like export { test, runTests } from "https://deno.land/[email protected]/testing/mod.ts"; seem to be the culprit.

they're not using all the available horizontal real-estate

see file_server.ts#L78

• Transition to Deno will be easier

I noticed a difference between 404 of wrong path of a good module and a bad module.

Bad path of a good module gives HTTP 404 Not Found response and a short body but no Content-Type header:

$ curl https://deno.land/x/dirname/wrong-file.ts
404: Not Found

But when there is a mistake in the module name, the status is 500 Internal Server Error with Content-Type: text/html; charset=UTF-8 and a lot of HTML, even when requested by curl:

$ curl https://deno.land/x/wrong-module/mod.ts
<!DOCTYPE html>
<!--[if lt IE 7]> <html class="no-js ie6 oldie" lang="en-US"> <![endif]-->
<!--[if IE 7]>    <html class="no-js ie7 oldie" lang="en-US"> <![endif]-->
<!--[if IE 8]>    <html class="no-js ie8 oldie" lang="en-US"> <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js" lang="en-US"> <!--<![endif]-->
[...]

If you are using netlify have you considered using Gatsby?

Would it make sense to allow the viewing / proxying of any repo from https://deno.land/x/?

e.g. something like https://deno.land/x/gh/USERNAME/MODULE_NAME@BRANCH/SCRIPT.ts for GitHub. Or maybe just https://deno.land/gh/....

Gitlab and others could be supported with alternate reserved prefixes. Just thinking about the long term editorial and maintenance contract of database.json. But maybe its perhaps intended as an editorialized / secondary std.

It seems like maybe the idea behind https://deno.land/x is similar to that of https://godoc.org and/or the go module proxy?

The current page load resource is too slow

And the loaded resource pack is too large

we should add babel-import-plugin plugin

Load components on demand

Then the component/router should be loaded dynamically

eg. Chart component

Files:

• https://deno.land/std/http/server.ts (OK)
• https://deno.land/[email protected]/http/server.ts (OK)

Indexes:

• https://deno.land/std/ (OK)
• https://deno.land/[email protected]/ (NOT FOUND)

(With no trailing slashes it's the same, plus additionally #116 happens.)

Perhaps due to interfaces? Related to #152?

I want people to be able to import pogo from 'https://deno.land/x/pogo', but right now that doesn't work because the registry doesn't know which file to point to.

It would be great if I could specify the main entry point in database.json.

I created module-url to make this a bit easier. It is a utility that takes an object as input, in nearly the same format as is used in database.json, and it returns a URL string of where to fetch the module from.

For example, the CONTRIBUTING.md links to contributing section of manual.md

• Source: https://github.com/denoland/deno/blob/master/CONTRIBUTING.md
• Link: https://deno.land/std/manual.md#contributing

When website loads https://deno.land/std/manual.md#contributing, it doesn't scroll to the contributing section

We already have more than 120 modules listen in registry. It'd be very useful to have a small search box at the top of the registry page than you could filter out the list.

I'd imagine that search box is focused by default when you visit the page and can be used to filter by name/description fields of the module.

as was done in denoland/deno#2919

cc @lucacasonato

https://deno.land/benchmarks
Example broken link: https://github.com/denoland/deno/blob/master/tests/003_relative_import.ts

Example:

• https://deno.land/x/dirname/ (with slash)
  • mod.ts links to https://deno.land/x/dirname/mod.ts (good)
• https://deno.land/x/dirname (without slash)
  • mod.ts links to https://deno.land/x/mod.ts (bad)

Additionally, the effect of a bad link is a blank screen with no 404 error or any other message.

Example:

• https://deno.land/x/nonexistent/path/name

Expected result: 404 error

What is visible: A quick flash of a header and a blank screen.

curl https://deno.land/x/ throws an 500 error from Cloudflare.

This causes failure of awesome-bot checks for denolib/awesome-deno