Mention the unsupported web APIs on the Deno Docs landing page

[ttogola]

Currently, anyone interested in Deno Deploy who reads the marketing page or the first few pages of the Deploy Docs might assume that anything that works in Deno will work in Deno Deploy. That is not the case, and it only becomes obvious when you run into a deployment failure or you scan the full docs until you find this runtime API Reference page:

It's different from Deno but aims to have similar APIs where applicable.

My suggestion is to make that fact stand out when entering the documentation, instead of leaving those important details buried. I found at least 2 feedback issues that were submitted because people weren't aware of the unsupported APIs.

For context, I ran into this because my toy project uses the Web Worker API. It works locally with Deno CLI, but Deno Deploy crashed with ReferenceError: Worker is not defined.

[timfish]

Some of these APIs should just be stubbed out with sensible defaults. I just hit an issue with navigator.hardwareConcurrency not existing.

[MarkBennett]

This would be a good opportunity to make the Deno Deploy docs into a public repo so the community can contribute pull requests.

[vwkd]

@MarkBennett #134

[MarkBennett]

@MarkBennett #134

Thanks, I've just subscribed to that issue!

[kleisauke]

FWIW, https://workers.js.org/#browser-apis provides a comprehensive list of browser APIs supported across various worker runtimes, which could also be used as a reference.