Yoshiya Hinosawa

example failure https://github.com/denoland/deno_std/runs/6812327594?check_suite_focus=true

context: https://github.com/denoland/deno_std/pull/2301/files#r891541278 `parse` options (`string`, `boolean`, `alias`, `collect`, `negatable`) are validated roughly. These should be validated more strictly

- `yarn add npm` (in compat mode) failed at https://github.com/denoland/deno_std/actions/runs/2357731220/attempts/1

compat: add dgram.Socket

2

`dgram.Socket` is needed to run [multicast-dns](https://www.npmjs.com/package/multicast-dns) in compat mode. (feature request from community)

Include /x/redis as /std/redis

3

There seem strong demands/needs of redis client in the community. We should have one in std ref: https://deno.land/x/redis ref: https://news.ycombinator.com/item?id=31333025 External dependencies of /x/redis: - lodash-es/shuffle - lodash-es/sample - lodash-es/uniqBy...

Some util.inspect (of `node/`) test cases fail with `Fatal process OOM in RegExpCompiler` in ubuntu

3

Since https://github.com/denoland/deno/commit/0ee76da07b12fba38962634e65853d73adf9d4c0 `test-util-inspect-getters-accessing-this.js` test case crashes with `Fatal process OOM in RegExpCompiler` only on Ubuntu You can check it with the below steps on ubuntu ```ts $ deno upgrade --canary...

ref https://github.com/denoland/deno_std/pull/2093#discussion_r862336747

Got feedback from the community that the reason of deprecation of fs.exists are not enough clear, not enough understandable and that alternative solutions are not clear. We should document these...

We probably can use [act](https://github.com/nektos/act) for testing our github action in CI