Jayden Seric

Yes: https://chromedevtools.github.io/devtools-protocol/tot/Input/#method-dispatchMouseEvent I wonder if touch events, and other input events, need attention too.

The defaults should absolutely not be biased to Jest. If Zed has to have a default test runner, it should be the native Node.js test runner: https://nodejs.org/api/test.html#test-runner

There is `v1.4`, but for v1.5 you have to do just `1.5`. The tags are a sick joke: https://github.com/superfly/flyctl-actions/tags Look at all the variations for v1: - https://github.com/superfly/flyctl-actions/releases/tag/v1 - https://github.com/superfly/flyctl-actions/releases/tag/1...

Duplicates https://github.com/mui/material-ui/issues/32846 .

@benjie > When doing so you may wish to note the application/x-www-form-urlencoded and multipart/form-data approaches have also both been used in the past by various clients/servers, but that they have...

With Deno v1.36.4 (and some older versions too), running: ```sh deno run \ --allow-env \ --allow-net \ --allow-read \ --allow-write \ https://deno.land/x/[email protected]/install.ts ``` Results in this error: ``` error: Uncaught...

@phryneas > Reading this, I feel like this is heavily skewed towards a very specific consumer: unbundled ESM over HTTP And it feels like it doesn't take other use cases...

To clear up confusion about avoiding waterfalls with ESM over HTTP, let's go over a hypothetical scenario… #### Module graph ```mermaid graph LR A[a.mjs] --> B[b.mjs] A --> C[c.mjs] C...

It's also an anti-pattern to use `~` instead of `^` for the version range.