Yoshiya Hinosawa

There seem a few concerning points to this move: - There seem no alternative way to support synchronous I/O using ReadableStream based APIs. - The support of **seek** behavior will...

sync behavior might be implemented as [`FileSystemSyncAccessHandle`](https://developer.mozilla.org/en-US/docs/Web/API/FileSystemSyncAccessHandle) in the future `seek` is available in [`FileSystemWritableFileStream`](https://developer.mozilla.org/en-US/docs/Web/API/FileSystemWritableFileStream/seek), but I couldn't find a way to seek during reading in Web APIs

Note: `Deno.umask()` is racy ref. https://github.com/denoland/deno/issues/13632

PRs trying to update chalk in next.js: - https://github.com/vercel/next.js/pull/41730 - https://github.com/vercel/next.js/pull/11268

Do we remove `.env.example` and `.env.default` handling before the stabilization? related #5018

the stabilization process follows these steps https://github.com/denoland/deno_std/issues/4661

`types.ts` file seems unnecessary to me as the types in it are not shared with other scripts. I think that should be merged in `parse.ts` Can you also write some...

Yes, we now recommend the users should use version range dependency like `@oak/oak@^16.0.0` or `@std/path@^0.224.0`. These module specifiers will automatically get fixes and new features, if you run the program...

@halvardssm > I could see an alternative versioning scheme instead that could potentially work better: > ... > patch versions would not introduce breaking changes, but minor versions could. This...

@KnorpelSenf I think we are still open to the idea of single versioned standard library in some form (such as https://github.com/denoland/deno_std/issues/4327 . Let's keep this discussion there), but right now...