You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ Instead of trying to assemble a hodge-podge collection of PostCSS plugins that "
16
16
* Less.js does not save "raws" when parsing. It also only preserves the start line / column of your source, which is still fine for Source Maps.
17
17
18
18
## How is this different from a Less plugin?
19
-
A plugin like [less-plugin-autoprefix] parses your CSS twice. First, [Less.js] parses your `.less`, evaluates it, and outputs CSS as a string. Then, PostCSS parses the string to make an AST. The [postcss-less-parser] plugin directly converts the evaluated Less AST to a PostCSS AST without re-parsing. WHICH WAS REALLY HARD.
19
+
A plugin like [less-plugin-autoprefix] parses your CSS twice. First, [Less.js] parses your `.less`, evaluates it, and outputs CSS as a string. Then, PostCSS parses the string to make an AST. The [postcss-less-engine] plugin directly converts the evaluated Less AST to a PostCSS AST without re-parsing. WHICH WAS REALLY HARD.
20
20
21
21
I'm not sure if that would have a major performance difference or not. Someone else can do the benchmarks, my brain is full.
22
22
@@ -25,30 +25,30 @@ I'm not sure if that would have a major performance difference or not. Someone e
0 commit comments