jakecastelli

Just had a quick scan, looks like the current main does not have `path` property any more? was that intentional? (it was still there in `v20.x`, `v22.x` and I couldn't...

Hi @benjamingr, I understand your concern. In my opinion the current behaviour in the browser isn't ideal either. According to MDM documentation on `setTimeout` ([also here](https://developer.mozilla.org/en-US/docs/Web/API/setTimeout#non-number_delay_values_are_silently_coerced_into_numbers)): > Also note that...

> make it harder to write universal code I think we only emit run time warning _instead of throwing an error and preventing the user from passing NaN or negative...

Appreciate your explanation @benjamingr 🙏 I am a bit mixed on your opinion. Please let me explain a few of my thoughts here: > libraries would start emitting a warning...

> Do you think we could address this concern by adding a sentence to clarify that this is not the case? I think this is a fair take, would add...

Hi @benjamingr would you mind taking another look 👀 when you have some time

Hi guys, thanks for all your participation and input! I have been thinking about this one. And I would like to write my findings (there is no doubt I will...

> Marking as semver-major because emitting a warning is not a documentation-only deprecation. Hi @tniessen, when I first opened this PR I didn't know what depreciation cycle means, so my...

Since https://github.com/nodejs/node/pull/53513 has landed, I think I should close this PR now. Thanks everyone! If you have some time, please take a look at the runtime warning PR https://github.com/nodejs/node/pull/46678

Just tested it this as well, if adding `*` after `temp` it will say `no matches found: --allow-fs-write=/file path/`