2024 FSCSS vs 2026 FSCSS — still moving, still light, still backward-compatible
Looking back at my 2024 article 😅
https://dev.to/figsh/my-rotate-animation-css-fscss-46b
2024 FSCSS vs 2026 FSCSS
Still moving with FSCSS 😕
Code written for v1.1.3 still runs fine on v1.1.26.
No breaking changes.
Backward compatibility is still a real thing here.
What was already there early:
- Animation compact - since 1.1.0
- Arrays - since 1.1.2
-
%n(),$variables,-*vendor prefixing… - since the unreleased days
What came later:
-
v1.1.24 -
@define+ selective@import -
v1.1.25 – 1.1.26 -
pattern()(write what you mean, let the compiler match it) - https://dev.to/fscss/pattern-in-fscss-write-what-you-mean-let-the-compiler-match-it-541m
The hardest recent release (and my favorite)
The real upgrade was the @import that can pull @define blocks and rename them on the fly:
@import((yourname as myname, brother as bro) from "/me.fscss")
@bro()
@myname()
Because it works directly with @define:
load - read - edit - paste…
Still light. Still pure CSS at the end.
Where everything lives
- Docs - fscss.devtem.org
- Learning hub - hub.devtem.org
- npm - npmjs.com/package/fscss
- One of the modules - github.com/fscss-ttr/st-core.fscss
A small note on the JavaScript journey
I’ve been simplifying some possibilities ❤️
Less noise. More direct paths.
Thank you to everyone who keeps sending heads ♥️❤️
I see you.
Still building.
Still light.
Still moving. 🎉
Top comments (0)