Define your styles in TypeScript!
This might seem odd - why would you define styles in TypeScript and not in a specialized language like CSS or SCSS? Because this allows us to leverage the full power of TypeScript. Have you ever tried making and managing one of those janky SCSS arrays / did you ever use arrays in TypeScript? You can assemble, combine, generate, theme, inherit, extend, ... your styles on both the server or client with the power of TypeScript.
This framework aims to translate all the CSS features into typescript, while adding type safety. You may combine this with other libraries which add preassembled mixins, err i meant functions, and classes to help with flex, ...
We do not have the resources to add every single CSS property into @acryps/styles, so we only added the properties we use for our applications. If something is missing, please open an issue or create a pull request and we'll try to add it asap.
This does not define any styles or mixins on its own.
Basic styles with fixed variables.
style returns a StyleDeclaration, which can be applied in DOM contexts by calling .apply() or converted to a CSS source string using .toString()
const primaryColor = rgb(132, 33, 187);
const spacing = rem(3);
style('ui-book',
display('block'),
child('ui-title',
display('block'),
marginBottom(spacing)
)
child('a')
.after('→',
color(primaryColor)
)
).apply();Adding a dynamic CSS variable.
Note that .update will apply a new value to the DOM only on DOM contexts, while on contexts without a DOM, like node, this will just update the value definition, thus the console.debug will output the new color at the variable definition.
let primaryColor;
const spacing = rem(3);
const layout = style('ui-book',
primaryColor = new Variable('primary-color', rgb(132, 33, 187)),
display('block'),
child('ui-title',
display('block'),
marginBottom(spacing)
)
child('a')
.after('→',
color(primaryColor)
)
).apply();
button.onclick = () => {
primaryColor.update(hsl(deg(51), 100, 40));
console.debug(layout.toString());
}Making a helper, or mixin
const primaryColor = rgb(132, 33, 187);
const spacing = rem(3);
const header = () => [
display('block'),
marginBottom(spacing)
];
style('ui-page',
child('ui-book',
display('block'),
child('ui-title', header())
).apply();
child('ui-author',
display('block'),
child('ui-title', header())
).apply();
).apply();Some of the specs are weird, but we try to implement them as is.
Use backgroundColor(hex('f00')) instead of background(hex('f00'))
background is a shorthand to define multiple background layers at once, whereas background-color is the proper property to set multiple layers of background colors.
Use textDecorationLine('underline') instead of textDecoration('underline').
text-decoration is acutally a shorthand consisting of text-decoration-color, -line, -style and others.
When using multiple text decorations, use textDecorationLine('underline', 'line-through').
Use filter(opacityFilter(1)) instead of filter(opacity(1)).
There are two things called opacity in CSS: The opacity: 1; property, and the opacity(1) filter layer.
To prevent conflicts, we renamed the less used opacity filter.
We have tried using official declaration lists, like @webref/css or mdn-data.
Sadly, even the official declarations contain errors, which broke the parser (check out old commits) multiple times.
But there was a bigger issue: You can't automatically map css declarations to useful typescript APIs.
There are always a ton of declaration options for the same property, which we cannot make type safe.
After long consideration, we thus chose to make them manually.
There are a lot of CSS properties, often repeated over and over again using different axis or sides (left, right, ...).
The properties defined in source/declarations are generated from declare, using npm run declare.