1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
/*!
* future-css -- https://github.com/estith/future-css
* A styling system for multi-language, multi-platform systems
*
* Regenerate with: npm run build
* This file is generated; edit the sources in src/ instead.
*/
/*!
* future-css -- layer order
*
* This file exists to be imported FIRST and on its own, so the cascade layer
* order is established before any layer's contents arrive. Consumers who load
* pieces separately must import this first:
*
* import "future-css/layers";
* import "future-css/tokens";
* import "future-css/base";
*
* Layer order determines precedence regardless of source order, specificity, or
* `!important` inside a lower layer. The sequence below is the whole cascade
* strategy of the system:
*
* reset zeroes out what browsers get wrong. Zero specificity.
* tokens the variables. Everything downstream reads from these.
* base element defaults. Zero specificity, so never fights a class.
* layout structural primitives.
* components individual components.
* utilities the escape hatch; beats components on equal specificity.
* overrides a reserved final layer for consumer-level escape hatches.
*
* The two properties that matter most:
*
* 1. `base` at zero specificity means a component class always wins over an
* element rule, with no `!important` and no specificity war.
* 2. `utilities` last means an author can always override a component with a
* single class, which is what makes the system debuggable in production.
*/
@