Divy
Divy
Fixed with `DENO_FUTURE`
https://github.com/swc-project/swc/issues/571 might be an interesting one to keep an eye on.
Maybe we can use #[serde(deny_unknown_fields)] for the config and print the error?
Adding an `import process from "node:process"` in `data/siteMetadata.js` fixes the issue
Unblocked. This can be implemented now.
A max length is set to prevent large string output from being too overwhelming. I agree, let's update `maxStringLength` to 10_000. Ref: https://github.com/nodejs/node/pull/32744
> what exactly these people were thinking > These people must not work with console output or do anything serious @e3dio You are violating our [Code of Conduct](https://github.com/denoland/deno/blob/main/.github/CODE_OF_CONDUCT.md): - Please...
@iuioiua FYI I don't think I'll have time to get this in for 1.41. It's a little more work than I thought - will keep you updated
We would need some code (atleast the `serve` handler) to investigate this. The error occurs when the response returned from the `serve` handler is not the same one returned by...
Closing as it seems this has been answered.