Ryan Christian

Build tooling isn't likely to matter in a types issue, but regardless, it's just an example of scope that's appropriate. But thanks, the minimal repro does help. Looks like we'll...

I'll mark this as "ready", though I'm happy to still discuss whether we even want to do this and how it should interact with other things like RTS. IMO, it...

> The other tidbit I wanted to add to this discussion is that we do technically already have a "force to use attribute" syntax, which is to uppercase the name...

Not at this time. `data-` attributes, being user defined, I don't think can be safely treated as boolean attributes? It's impossible for the framework to know whether you expect to...

I don't think we want to get into every possibility; I'm not sure even explicit prop/attr directives will land as-is. If you want boolean, probably going to be on you...

> Answer: it depends, sometimes Preact sets the `.foo` property, sometimes Preact sets the `foo` attribute. The user has no control over this. While I don't disagree with the premise/request,...

Not quite what I meant, no. We largely set what we set, we're not looking to satisfy any scenarios beyond "works with DOM APIs correctly". Anything beyond that is a...

@rejhgadellaa ~~have you checked the latest version?~~ I believe that was a bug that was corrected. Edit: Never mind, hasn't been released yet. Fixed in #4393 though

It's an issue others have mentioned before, but ultimately, this is a completely valid configuration we have here and it's other tools that are causing the issue. Using the `exports.browser`...

> Out of curiosity, what are the differences between the preact.module.js and preact.mjs? None at the moment, and I think the latter is even generated from the former. We could...