Fredrik Nicol

Related https://github.com/mdn/data/pull/425

Please read the [contributing](https://github.com/frenic/csstype#contributing) section before opening a PR. [This file](https://github.com/frenic/csstype/blob/master/src/data/svg.ts) should be patched, not `index.d.ts` directly.

The `main` field is the same as `@types` packages which is just `""`. There could be other issues when adding a `.d.ts` file to `main` so I'd say it's better...

Maybe the answer to your issue can be found here https://github.com/import-js/eslint-plugin-import/issues/1341?

It actually up to vendors to decide if they want to support CSS Custom Properties by default or not. But the only way is to support them out of the...

Hopefully https://github.com/microsoft/TypeScript/issues/6579 will become reality soon and we could do something like: ```ts interface Properties { // .... [customProperty: /--\w+/]: number | string; } ```

I agree with @cyrilchapon. Custom properties are what they are, custom properties. And it's impossible to automatically know **your** custom properties. So end users are forced to specify them somehow....

I'm not sure I'm following but it's quite simple to hyphenate style properties (inspiration from [Glitz](https://github.com/frenic/glitz/blob/master/packages/core/src/utils/parse.ts)): ```js const style = { color: 'white', textAlign: 'start', }; const hyphenateRegex = /(?:^ms)|[A-Z]/g;...

The syntax is quite alike `align-content` so I guess it will solve itself when it's done 😃

Syntax entities are now grouped by combinator precedence. The identification whether a component should be included or not is simplified but will likely be revised when component combinations will be...