Divy

Closes https://github.com/denoland/deno/issues/22315 ``` ~> DENO_FUTURE=1 target/debug/deno > globalThis.window undefined ```

And `--allow-dirty` to bypass this. Similar to `cargo publish`.

Consider the default Next.js app example. A user has to know what "byonm" is to be able to run the project with Deno: ``` deno run -A npm:create-next-app@13 && cd...

`deno publish` triple slash directions allowed in dry-run.

1

``` divy@mini ~/g/pasteboard (main)> deno publish Checking fast check type graph for errors... Ensuring type checks... Check file:///Users/divy/gh/pasteboard/pasteboard.ts Visit https://jsr.io/auth?code=XXXX to authorize publishing of @divy/pasteboard Waiting... Authorization successful. Authenticated as...

Reproduction from Next.js on Windows: ```js import etag from "npm:etag"; import {statSync, Stats} from "node:fs"; const stat = statSync("README.md"); etag(stat); ``` ``` error: Uncaught (in promise) TypeError: argument entity must...

Implement `node:wasi`

3

`std/wasi` is being deprecated https://github.com/denoland/deno_std/pull/3732 and it would be nice to offer an alternative i.e `node:wasi` before it's removal. Some ideas on perfomance: - https://github.com/littledivy/fastwasi - https://github.com/denoland/deno_core/pull/289

Issue https://github.com/denoland/deno/issues/22222  This PR moves `runtime/permissions` code to a upstream crate called `deno_permissions`. The `deno_permissions::PermissionsContainer` is put into the OpState and can be used instead of the current trait-based...