Christian Bewernitz

Yes, most of the implementation is using plain properties even for fields that contain the same data. Fixing that everywhere would be a huge effert and will most likely only...

starting from https://github.com/xmldom/xmldom/releases/tag/0.9.0-beta.9 (available under `@xmldom/xmldom@next`), a `ParseError` is thrown when the `documentElement` is not present after parsing is done. This behavior was introduced as part of #454

Not any progress other then discussions. All discussions regarding different supported or unsupported runtimes can be found in https://github.com/xmldom/xmldom/discussions/214 And I started a poll regarding node versions to support in...

Just to mention it here, since I think it's quite relevant: I recently discovered https://github.com/bwrrp/slimdom.js which seems to be a straight forward, well tested alternative which is already written in...

This alternative seems to provide a much better DevX: https://github.com/marketplace/actions/github-deployments

The main problem I see with this destructive action being enabled is the conflict it causes for repos that use conventional commits, in which case it is important to add...

> We think it's good default and those who disagree can already disable it *and* are alerted every time. This means: > > - we won't drop the feature >...

Since we are still using React 17, we are still using `@chakra-ui/*@1` and we are also experiencing this issue when trying to upgrade typescript to 5.0.3. Any plans to provide...

Is this something that is specific to chakra-ui v2? I'm not able to find any occurrence of `jsxImportSource` in our codebase that uses v1

@TimMensch as I described in https://github.com/chakra-ui/chakra-ui/issues/7526#issuecomment-1510358596 we are still using react 17, and my current understanding is that chakra-ui v2 requires react v18, so we will not be able to...