Jordan Pittman
Jordan Pittman
This is a work in progress. I'd like to see if this is a reasonable approach or if there are better ideas. My first thought was to turn candidates (conditionally)...
Fixes #280 There are some bugs in Tailwind's own selector rewriting for variants but also some bugs in our own selector rewriting. Use `postcss-selector-parser` to more properly handle selector rewriting...
# This is a work in progress — much is still broken and all features documented or otherwise are subject to change I'm opening this PR now to solicit feedback...
This is broken: ``` const mix = require('laravel-mix') mix.vue() mix.extract() mix.options({ hmrOptions: { host: '0.0.0.0', port: 8080, }, }) mix.js('resources/js/site.js', 'public/js') //
There's a lot of oddities around `@apply`, it's implementation, what it supports and doesn't. Ultimately this produces a lot of unexpected behavior because people expect it to work one way...
When nesting an `@layer` inside a style rule it's properly lifted but multiple layers with the same name are not merged — whether minified or not. This merging typically happens...
From [Discord](https://discord.com/channels/486935104384532500/1217407069053780028/1218820631575924766): ``` Hi. I discovered what the cause was but I'm not sure it's really relevant or useful. So I'm not sure if I should still file an Issue...
# The Problem First off I know this is a bit odd but, when parsing a selector with a comment before it PostCSS will treat it as a comment node....
In Firefox Nightly, when using properties that declare the shorthand syntax ``, there is a bug where two properties side-by-side e.g. `var(—foo)var(—bar)` invalidate the property value when it should not....