Deno strives to be browser compatible where possible; that means we use quite a few Web APIs.

There is not much docs for supported Web APIs at the moment and before 1.0 is released that situation must change. Some of APIs and not fully aligned to spec, while others are not fully implemented (#3557). All that knowledge should be written down and presented to end users to avoid multiple question

Issue Type

• Bug Report
• Feature Request
• Other

Expected

$ command subcommand --help

Subcommand is used to... <---- this would be nice to be able to add

Usage:
  $ command subcommand

Options:
  -v, --version  Display version number
  -h, --help     Display this message

Actual

$ command subcommand --help

Usage:
  $ command

Currently these point to std@v0.38.0 but should be removed and replaced with something else.

see tests/pad.ts, tests/importmap.json and tests/importmap.ts.

Perhaps delay from https://deno.land/std@VERSION/util/async.ts ?

Whole documentation is just a README file, better documentation should be provided as documentation page.

Public API should be annotated with JSDoc, so auto generated API reference can be obtained.

The examples contained with pogo are very basic.

• working with request objects should be demonstrated
• working with path parameters should be demonstrated

import pogo from 'https://deno.land/x/pogo/main.js';
server.router.put('/path/{id}', async (request:pogo.Request) => {
    var id:String = request.route.params.id;	
});

• working with request body should be demonstrated

Atm now-deno uses the latest release but I think it would be good for users to (optionally?) pass a version number for the deno-lambda release to use.

(In the future this will match the deno version.)

Description

• Install deno
• Install the extension
• capture the usage with some tool and convert into a gif
• post the screenshot as a comment and once I approve it create the PR

Useful links

• https://deno.land/