`deno cache` consistently failing with the same error
negotiation file, sometimes it's other dependencies also from deno.land/std that's running into the issue.
Any clues on how to fix this?...Does fetch() support upgrading the connection to a websocket?
fetch() gets the response
```
HTTP/1.1 101 Switching Protocols
connection: upgrade...Error: Not implemented: crypto.Sign
Deno Deploy KV: Gateway Timeout

Slow loading time on localhost

Prisma error when trying to push/migrate db
Does the deno-astro-adapter will be updated to use astro 4? https://github.com/denoland/deno-astro-a
(In IntelliJ) Deno: Failed to load the import map at <absolute_path> (...)
serde_v8::from_v8 for BigInts unsupported through `deserialize_any`
deserialize_any path: https://github.com/denoland/deno_core/blob/main/serde_v8/de.rs#L131). This means that, for example, an object containing a field with a BigInt value cannot be deserialized. I assume this is because it's unclear which rust type to map it to?
If so, are there any issues with the following mapping rules?
- If the BigInt < 0 and within i64 bounds, then deserialize as i64
- If the BigInt >= 0 and within u64 bounds, then deserialize as u64...import plotly.js : invalid or unexpected token ?
import Plotly from "npm:plotly.js-dist"; yields
Stack trace:
SyntaxError: Invalid or unexpected token at file:///Users/george/Library/Caches/deno/npm/registry.npmjs.org/plotly.js-dist/2.28.0/plotly.js:1091:14
...Deno deploy: "Error The deployment failed: ISOLATE_INTERNAL_FAILURE"
Module documentation preview in development
deno doc command, but it does not support watch mode. I guess that the easiest solution with the current tooling would be to run deno doc --html whenever a code changes, and serve the resulting html using some live-server that would check for changes as well. Not a great solution.
Next, I was looking into https://github.com/denoland/docland and use the deno_doc package in combination with Fresh to get automatic refresh of the documentation. I was not able to make this work though since I am using some npm references and the deno_docis not able to load that using the default loader....Fresh project creation hanging

Redirect which deno deploy instance is used?
std/http/setCookie doesn't work?
Abort signals and node compatibility
AbortSignal types are not compatible. I have verified that I can use a deno AbortSignal with the node:events APIs (at least EventEmitter.once(), but I have to cast them to Node's own type if I want to get rid of errors:
```ts
export { EventEmitter } from 'node:events'
export type { AbortSignal as NodeAbortSignal } from 'npm:@types/node'...
deployctl error: TypeError: request or response body error