overlapui ships two products that look related but serve different users:
overlapui.fscss — the real module: @define s, selective @import , token helpers, compose only what you need.
overlapui.css / .min.css — a precompiled drop-in sheet for people who never touch FSCSS: link it, use the utility classes, ship.
That second path raises a fair question: can every other module in the ecosystem do the same?
Short answer: most can ship a plain CSS build; not all should treat it as the primary product. The limit is not “FSCSS can’t compile to CSS” — it always can. The limit is what you lose when you freeze a parameterized module into one fixed stylesheet.
What a “plain CSS version” actually is
It is not a second language implementation.…