Pascal Duez

> Regardless I'd go with a fixed length instead of `rem` so it's not influenced by what the root `font-size` is. Agree, I will do that. Let's use this little...

Hi @shoonia, so what's the question / issue then ? Yes, I noticed this change as well. But I don't feel like it's a rule this preset should deal with.

I think the [`value-keyword-case` rule](https://stylelint.io/user-guide/rules/value-keyword-case#value-keyword-case) is not only targeted at the `composes` property, but any property value that could potentially use a keyword with casing style. That's a style decision...

Hi, this project is actually not a plugin but just a config, grouping already available rules. What you describe would indeed need a plugin with some cutom rule(s).

I guess if there's a need for more specidifc rules then yes we could write a plugin. The naming would be different (`stylelint-css-modules` for instance) so obviously another package. And...

I just went with an IIFE: ```js {(() => { const [possible, setPossible] = React.useState(false); return ( setPossible(true)}> Can I use state in playroom: {possible ? "yep" : "dunno"} );...

> but only recently became possible because the internal component that wraps your JSX used to be a class component, so Hooks were not supported That's it! I remember an...

We have the same experience. This would need to be configurable in a way, for private installs of playroom that can't rely on external third party services for the short...

@HenryKenya Still relevant, be welcome! The ideal procedure in this case, split the changes into several commit: - clone from the v2 defs - Flow updates (probably needed) - v3...

Like you said, as long as the added types are properly tested, and maybe a few comments added at the top of the libdef, it's all fine. We already accepted...