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
+6-5Lines changed: 6 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,15 @@
1
-
## Interoperable CSSinJS standard format.
1
+
## Interoperable CSSinJS standard.
2
2
3
3
The biggest issue at scale we currently have with all CSSinJS implementations is that they are not sharable without the runtime.
4
4
5
-
We can define a format that is easy to parse and supports all the needs of the current CSSinJS implementations on top of CSS.
5
+
Using regular CSS doesn't support all features we need. CSS notation is designed for humans and is too slow for parsing.
6
6
7
-
Package maintainers will be able to publish JavaScript files to NPM using this format instead of plain CSS or any variation of objects notation.
7
+
This format is [blazingly fast](https://esbench.com/bench/592d599e99634800a03483d8) to parse and will support all needs of the current CSSinJS implementations.
8
8
9
-
## First draft
9
+
Package maintainers will be able to publish JavaScript files to NPM in this format instead of plain CSS or any variation of objects notation.
10
+
11
+
Do not confuse this format with an AST. It is designed purely for interoperability and publishing. Using this format you can build an AST or regular CSS or any other structure.
10
12
11
-
Format is optimized for parsing in JavaScript, not for human readability.
0 commit comments