Alec Larson
Alec Larson
It's not really a bug, just a limitation. Something is only a bug if it's a documented behavior that isn't working as expected. You're actually making a feature request. Semantics...
That's not a polyfill, it's called syntax downpiling. Libraries aren't responsible for such a thing, unless you're talking about a CDN build. Generally though, I would discourage using CDN builds,...
This issue is fixed in `[email protected]` (a fork of Radash).
Hello @arkark, if the same vulnerability exists in [Radashi](https://github.com/radashi-org/radashi) (a maintained version of Radash), please see our [SECURITY.md](https://github.com/radashi-org/radashi/blob/main/SECURITY.md) document for next steps.
You can do `err !== undefined`, but you really shouldn't be throwing anything other than `Error` objects, since you otherwise lose the stack trace, which can make debugging really difficult....
I agree. This should be fixed, as the current behavior is misaligned with JS `using` syntax ([link](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/using)): > If the scope contains multiple `using` or `await using` declarations, all disposers...
👋 Hi @alumni Over at the [radashi](https://github.com/radashi-org/radashi) fork, I've got two PRs that will fix this issue. - [#438](https://github.com/radashi-org/radashi/pull/438) adds an argument to `isEqual` so you can set a custom...
Hi @PaulMouchel, this is fixed in the Radashi fork ([#95](https://github.com/radashi-org/radashi/pull/95)). A lot of other stuff has been added/fixed too.
All compiler errors are now fixed.
I've updated the project setup in `./examples/sample` to use Expo 54.