Divy

Implemented in https://github.com/denoland/deno/pull/24101

Yes, that fixes the original error. Now I get another one: ``` divy@divy test-app-15]$ deno task dev Task dev next dev --turbo ▲ Next.js 14.3.0-canary.73 (turbo) - Local: http://localhost:3000 ✓...

Oh never mind, it works! (I wasn't using DENO_FUTURE=1 which removes window global) 

I'm getting 2x faster debug builds with `mold -run` as of fabd9a214b278bb119818187de66121c5f91b751 ``` [divy@divy deno]$ time mold -run cargo build -p deno --bin=deno Compiling deno_fs v0.62.0 (/home/divy/gh/deno/ext/fs) Compiling deno_node v0.89.0...

> is it a deliberate choice that process.kill now requires --allow-run permission This has always been the case as far as I can see in `git blame`. `--allow-run` is currently...

It's a regression from #23208 This `getcwd` code path should never reach with `--allow-all` and generic `--allow-read` https://github.com/denoland/deno/blob/fabd9a214b278bb119818187de66121c5f91b751/ext/fs/std_fs.rs#L904-L905

Really like the idea of providing suggestions. Here's a little more real-worldy next config: https://github.com/timlrx/tailwind-nextjs-starter-blog/blob/main/next.config.js Ideally Deno could provide suggestions for migration: ``` | const { withContentlayer } = require('next-contentlayer')...

Thanks for pointing out, I was solely relying on lint:docs to yell at me :)

Oh, the lint should probably detect that? I got an error for missing `@example` in `crypto`

@aapoalas lets do it