Yoshiya Hinosawa
Yoshiya Hinosawa
> Also can you confirm it's not possible or a good idea to use node apis conditionally when we detect we're not on the browser? I'm not in favor of...
probably duplicate of #3533 ?
Ah, ok. Then this would be a bit different feature request.
Something like the below should work: ```ts import { serveDir, serveFile } from "@std/http/file-server"; Deno.serve(async (req) => { const resp = await serveDir(req); if (resp.status === 200) { return resp;...
Does the utility like this make more sense to such cases? https://github.com/fent/node-stream-equal
`--fail-fast` currently only works for the top-level `describe` and `test` (The below test stops at `suite 1`, for example). So the issue here is `--fail-fast` doesn't work for nested test...
I wonder if this changed anything as there's still a test case which checks `mode === null` in Deno.statSync result on windows. https://github.com/denoland/deno/blob/04ae1a551726dd6e0047a942b459d18e1dcb1935/tests/unit/stat_test.ts#L274
I'm not actively developing this project anymore. I'd accept small non-breaking PRs (like adding `--no-bundle` option), but if you like to see more fundamental changes (like supporting many of esbuild...
This needs consensus in both core team and community. I'm personally not in favor of this change. I've never heard of the user feedbacks of getting confused by this structure....
The error message seems created in this line? https://github.com/denoland/deno_core/blob/7cbc5ae35c279972d46e5552b7a5978860df611e/core/webidl.rs#L96 Is it possible that CI machine's state affects this?