Simon Smith

@mlnmln Sounds good. I should have more time in 2019 to dedicate to OSS as well so perhaps we can work together on any pressing issues. Once everything is in...

For now I'd recommend using the `postcss-loader` and add the plugins you need. So something like: ``` js // postcss.loader.js const atImport = require('postcss-import'); const customProperties = require('postcss-custom-properties'); const customMedia...

@ShavidzeT Nice. We certainly need a more concise solution. I had actually started work on a webpack plugin for SUIT too. I'll add it to the org when I get...

I wouldn't be against the idea, but it does quickly move SUIT out of the 'future facing CSS' realm. Would be nice to be able to configure this to use...

I see, so each package would contain the output of the postcss tools? Could work. Might also give more weight to moving the packages into a single repo to facilitate...

We don't currently have any formal guidelines for custom properties, although there is a long [outstanding issue](https://github.com/suitcss/suit/issues/91) to get it all written up. I think it makes sense to allow...

> If it is enforced you won't have any choice but to release a major version. Nothing wrong with releasing major versions. I'd vote that if you have a namespace...

I'd be inclined to agree with @giuseppeg in that a utility should generally be unrelated to components. Configuring them with custom properties is rare, but a valid route to go...

Great, thanks. Might be related to #97

Hey @amk221 I've not encountered this use case but I'd agree it would be nice for the linter to permit it. A PR would be very welcome and I'd be...