React types without @deno-types before every import?
// @deno-types="npm:@types/react" above every single react import in every single file? I'm up-to-date with deno, I've got npm:@types/react in my types property of my compiler options, etc. I've been perusing issues and trying alternatives for hours, but it seems like this is the only option that actually works:
```
deno --versiondeno 2.1.5 (stable, release, aarch64-apple-darwin)...
how do I use `@ts-self-types` without `.d.ts` files appearing in docs?
.js and .d.ts where the .js files have // @ts-self-types="…" comments at the top.
And to make sure the Deno type checker can find the .d.ts files, they are all in the jsr.json's "exports" array....
TestContainers are broken in Deno.
Super slow LSP with Deno + VSCode
Deno compile with SupaBase doesn't work

Is Deno a good JS runtime for embedding into another application?
How to customize daisyui default theme?
I need ideas for different ways to dig into the Deno API's and its standard library
Relative import path "oak/router" not prefixed with / or ./ or ../ and not in import map
deno run -A src/main.ts.
deploy.yaml:
```yaml
# ......ONNX fails in Deno Deploy
Deno + SvelteKit + Paraglide | Can not run dev server using deno because of "FsWatcher"
error: module 'node:fs' does not provide an export named 'globSync'
`npm workspace`'s support with Deno v2
deno check main.ts, I get the following error:
```...Typescript monorepo LSP performance
Deno + drizzleORM

Reliable pattern for cleaning up resources as process exists?
await using resource = ...), but [Symbol.asyncDispose] doesn't get called if my program is killed with SIGINT or other signals. Is there a known/good pattern for making sure some resource gets cleaned up, even if the process is dying?
window.onunload, but since that's a global, it feels unreliable to rely on, since anything else in my dependencies might overwrite it during a lengthy runtime. I may also have more than one thing that I want to clean up.Deno.addSignalListener() but there are an awful lot of signals I'd need to listen to....Deno cannot use ErrorEvent Type from @types/ws
Cannot import type declaration files. Consider importing 'ws' instead of '@types/ws'.
import type { ErrorEvent } from "@types/ws";
Cannot import type declaration files. Consider importing 'ws' instead of '@types/ws'.
import type { ErrorEvent } from "@types/ws";
Why are both denols and tsserver attaching to the same TypeScript project in Neovim?
deno 2.1.5 not running in Azure Container App environment
FROM denoland/deno:latest in my Dockerfile and after the deno 2.1.5 release new replicas want deploy to CA environments, the container starts but immediately terminates.
Tried pulling the deployed image locally and it runs on my Windows PC on docker desktop without any issues.
I fixed the image to FROM denoland/deno:2.1.4 which solves the issue on Azure CA environment but think there might be some underlying compatibility issues....How can I add tailwindcss to a deno/vite/solidjs project?