---

Truss is a TypeScript DSL for writing utility CSS (think Tailwinds or Tachyons) in React/JSX, but on top of existing CSS-in-JS libraries (i.e. Emotion, MUI, and Fela).

Quick Features

Truss lets you:

• Write <div css={Css.mt1.black.$}>, which Truss turns into css={{ margin-top: 8px, color: "black" }}, and then Emotion (or another CSS-in-JS library) turns into injected CSS classes.

• Setup your project's design system (palette, fonts, increments, and breakpoints) in Truss's configuration (see example config and the "Customization" section below)

• Achieve both utility-class brevity and critical-CSS delivery.

• Output dynamic style values as needed, i.e. Css.mt(someValue).$ or Css.mt0.if(someCondition).mt4.$. And y

• Use selectors as needed, i.e. css={{ "&>div": Css.black.$ }} or Css.onHover.black.$, using your CSS-in-JS library's selector support

• Use Tachyons-based abbreviations for superior inline readability (see Why Tachyons)

• Leverage strongly-typed styles with just vanilla TypeScript

• Get immediate access to a built-in "cheat sheet", just control-click into abbreviations/methods to see what they do

Also see the "Why This Approach?" section for more rationale.

Quick Example

Here's an example of production code using Truss:

Quick How It Works

Truss generates a src/Css.ts file in your local project; this file exports a Css const that you use like:

import { Css } from "src/Css";

const css = Css.mx2.black.$;

The last .$ is like a .build() or .finish() method that converts the DSL object, with its fluent abbreviation getters/methods (like mx2 and black), into just a regular POJO (plain old JavaScript object), as if you'd written by hand:

const css = {
  // added by .mx2
  marginLeft: "16px",
  marginRight: "16px",
  // added by .black
  color: "#000000",
};

You can then pass this POJO to whatever CSS-in-JS framework you're using, i.e. with Emotion you would do something like:

/** @jsxImportSource @emotion/react */

function MyReactComponent(props: MyProps) {
  // Use emotion's css prop
  return <div css={Css.mx2.black.$}>content</div>;
}

And in your HTML output, you'd get an Emotion-generated .emotion-0 CSS class with the three marginLeft, marginRight, color properties set. (If you were to use Truss with Fela's fe JSX factory/css prop, you'd get three CSS classes, a, b, and c.)

See the "Common CSS-in-JS Frameworks" section below for Fela and MUI examples.

Installation

Truss is "just a single Css.ts TypeScript file", so does not require any special configuration of your app's bundling/build pipeline, but we do create a truss command to easily generate the Css.ts file from your truss-config.ts:

• npm i --save-dev @homebound/truss
• Add a truss command to your package.json:

  {
    "scripts": {
      "truss": "truss"
    }
  }

• Copy/paste an initial truss-config.ts into your project
  • wget https://raw.githubusercontent.com/homebound-team/truss/main/packages/template-tachyons/truss-config.ts
• Run npm run truss
  • Re-run npm run truss anytime you change truss-config.ts
• Start using Css.mt1.etc.$ in your project's CSS-in-JS setup

Note that for the css={Css.blue.$} syntax to work in JSX, you'll have to figure your CSS-in-JS library's React integration (i.e. for Emotion by setting the React importSource, see their docs).

We recommend checking the src/Css.ts file into your repository, with the rationale:

• Your design system will likely be pretty stable, so the Css.ts output should rarely change.
• When it does change, it can be nice to see the diff-d output in the PR for others to review.
• It's the simplest "just works" setup for new contributors.

Granted, you're free to not check-in src/Css.ts and instead .gitignore it.

Truss Command

The truss command accepts an optional second argument which is the path to your configuration file. If omitted, it will look for ./truss-config.ts.

{
  "scripts": {
    "truss": "truss path/to/configuration/file.ts"
  }
}

Configuration

Truss's configuration is done via a truss-config.ts file installed into your local project.

See the comments in that file for the available config options. For example setting up your custom font abbreviations is set via a FontConfig hash:

// Defines the typeface abbreviations, the keys can be whatever you want
const fonts: FontConfig = {
  f10: "10px",
  f12: "12px",
  f14: "14px",
  f24: "24px",
  // Besides the "24px" shorthand, you can define weight+size+lineHeight tuples
  tiny: { fontWeight: 400, fontSize: "10px", lineHeight: "14px" },
};

Also see the Customization section for more advanced configuration options.

Psuedo-Selectors and Media Queries

Unlike Tachyons and Tailwinds, Truss does not create duplicate/repetitive abbreviations/method names for psuedo-selectors and media queries (e.g. md-blue or lg-red).

Instead of building these complications into the DSL, Truss leverages your CSS-in-JS library's existing psuedo-selector and media query support.

For example, Emotion allows you to pass selectors keys in a map, so you can add :hover styling like:

function MyReactComponent(props: {}) {
  return (
    <div
      css={{
        ...Css.mx2.black.$,
        "&:hover": Css.blue.$,
      }}
    >
      ...
    </div>
  );
}

Or, you can create the same output using Truss's onHover command, which adds { color: "blue" } to the same &:hover key as in the previous example:

function MyReactComponent(props: {}) {
  return <div css={Css.mx2.black.onHover.blue.$}>...</div>;
}

You can also use media queries to create responsive breakpoints, again either using Emotion's "pass selectors as a key" syntax directly:

import { Breakpoints } from "src/Css";

function MyReactComponent(props: {}) {
  return (
    <div
      css={{
        ...Css.mx2.black.$,
        [Breakpoints.sm]: Css.mx1.$,
      }}
    >
      ...
    </div>
  );
}

Where sm is just a regular media query string, i.e. @media (max-width: 420px), that you can either generate with Truss's breakpoints config setting or just write your own by hand.

Or you can use Truss's ifSm, ifMd, etc. breakpoint commands (which will be based on your application's specific breakpoints defined in truss-config.ts):

import { Breakpoints } from "src/Css";

function MyReactComponent(props: {}) {
  return <div css={Css.mx2.black.ifSm.mx1.$}>...</div>;
}

This leveraging of the existing library's selector support makes Truss's DSL shorter and simpler than Tachyons/Tailwinds, which have to repetively/pre-emptively mixin hover/media variations for each size into each abbreviation.

Supported CSS-in-JS Frameworks

Truss generates a TypeScript/Css.ts DSL that, without any changes, can be used in MUI, Emotion, and Fela.

See the ./integration-test directory in Truss's repo for running unit tests for each of the these frameworks.

Emotion

function FooComponent() {
  return <div css={Css.black.$}>root</div>;
}

Fela

function FooComponent() {
  return <div css={Css.black.$}>root</div>;
}

function FooComponent() {
  const { css } = useFela();
  return <div className={css(Css.black.$)}>root</div>;
}

MUI

const useStyles = makeStyles({ root: Css.black.$ });

function FooComponent() {
  const styles = useStyles();
  return <div className={styles.root}>root</div>;
}

XStyles / Xss Extension Contracts

Truss liberally borrows the idea of type-checked "extension" CSS from the currently-unreleased Facebook XStyles library (at least in theory; I've only seen one or two slides for this feature of XStyles, but I'm pretty sure Truss is faithful re-implementation of it).

As context, when developing components, you often end up with "properties that are okay for the caller to set" (i.e. that you as the component developer support the caller setting) and "properties that are not okay for the caller to set" (i.e. because the component controls them).

Basically, you want to allow the caller to customize some styles of the component, typically things like color or margin or font size, but not give them blanket control of "here is a className prop, do whatever you want to my root element", which risks "radical"/open-ended customization that then you, as the component developer, don't know if you will/will not unintentionally break going forward.

(I.e. see Layout isolated components for a great write up of "parents control margin, components control padding".)

With Truss, you can explicitly declare a contract of styles allowed to be set on your component, i.e.:

import { Css, Only, Xss } from "src/Css";

// Declare the allowed/supported styles
export type DatePickerXss = Xss<"marginLeft" | "marginRight">;

// Update the props to accept an `xss` prop to accept the customizations
export interface DatePickerProps<X> {
  date: Date;
  xss?: X;
}

// Use the `Only` type to ensure `xss` prop is a subset of DatePickerXss
export function DatePicker<X extends Only<DatePickerXss, X>>(props: DatePickerProps<X>) {
  const { date, xss } = props;
  // The component controls marginTop/marginBottom, and defers to the caller for marginLeft/marginRight
  return <div css={{ ...Css.my2.$, ...xss }}>{date}</div>;
}

Here we're allowing callers to set marginLeft or marginRight, i.e. this line will compile because mx2 is statically typed as { marginLeft: number; marginRight: number }, and so is a valid xss value:

<DatePicker xss={Css.mx2.$} date={...} />

However, this line will not compile because mt2 is statically typed as { marginTop: number }, and marginTop is not allowed by DatePickerXss:

<DatePicker date={...} xss={Css.mt2.$} />

The Css DSL also iteratively types itself, i.e. Css.ml1.mr2.$ is still statically typed as { marginLeft: number; marginRight: number }, instead of being based just on the last-used abbreviation.

Note that Truss conventionally uses the xss prop name for "the component's allowed extension styles" as a play on Emotion's css prop, with the x representing the "extension" concept. But there is otherwise nothing special about the name of the xss prop; i.e. you could use xstyles={...} which I believe is what the Facebook XStyles library does, or your own convention.

Also note that the XStyles/Xss feature is completely opt-in; you can use it if you want, or you can use Truss solely for the Css.m2.black.$ abbreviations.

Customization

Truss supports several levels of customization:

1. Per-project fonts/colors/etc. in truss-config.ts
2. Per-project rule additions or changes in truss-config.ts
3. Forking

Per-Project Fonts/Colors/Etc

Each project that uses Truss gets a local index.ts, checked into its repo essentially as a config file, that defines in TypeScript the core settings, i.e.:

const increment = 8;
const numberOfIncrements = 4;

const palette = {
  Black: "#353535",
  MidGray: "#888888",
  LightGray: "#cecece",
  White: "#fcfcfa",
  Blue: "#526675",
};

const fonts = {
  f24: "24px",
  f18: "18px",
  f16: "16px",
  f14: "14px",
  f12: "12px",
  // Can also set multiple properties if necessary
  f10: { fontSize: "10px", fontWeight: 500 },
};

const breakpoints = { sm: 0, md: 600, lg: 960 };

// ...rest of the config file...

Projects should heavily customize these settings to match their project-specific design system, then run npm run truss to get an updated Css.ts, i.e. after adding Green: "green" as a color in palette, the Css.ts file will automatically have utility methods added like:

  get green() { return this.add("color", "green"); }
  get bgGreen() { return this.add("backgroundColor", "green"); }
  get bGreen() { return this.add("borderColor", "green"); }

Per-Project Utility Methods

In the same index.ts, projects can add their own new abbreviations/utility methods:

const sections = {
  ourSection: () => [newMethod("someAbbreviation", { color: "#000000" })],
};

Will result in Css.ts having a line that looks like:

  // ourSection
  get someAbbreviation() { return this.add("color", "#000000"); }

Which can then be used as Css.m2.someAbbreviation.$.

Besides adding one-off additional methods, if your project wants to replace a whole section of Truss's out-of-the-box methods, you can do this via:

const sections = {
  // Prefer app-specific border radiuses
  borderRadius: () =>
    newMethodsForProp("borderRadius", {
      br4: "4px",
      br8: "8px",
      br16: "16px",
    }),
};

Where borderRadius matches the name of the section in Truss's sections directory (which generally matches Tachyon's organization).

Forking

At the end of the day, Truss is small and hackable such that forking it to make the abbreviations "strict Tachyons" or "strict Tailwinds" or "whatever best fits your project/conventions/styles" should be easy and is kosher/encouraged.

The core Truss feature of "make a TypeScript DSL with a bunch of abbreviations" is also basically done, so it's unlikely you will miss out on some future/forthcoming amazing features by forking.

And, even if so, the coupling between Truss and your application code is limited to the Css.abbreviations.$ lines that should be extremely stable even if/as the core of Truss evolves.

Why This Approach?

Truss's approach is "Tachyons-ish" (or Tailwinds-ish), insofar as having short/cute utility class definitions.

However, the abbreviations are runtime resolved to object-style CSS-in-JS rules that are then injected into the DOM by Emotion (or your CSS-in-JS framework of choice), as if the rules had originally been written long-form.

The benefits of this approach are:

• We get the brevity + "inline-ness" of Tachyons/Tailwinds.

• It delivers critical CSS, i.e. we don't need the large static TW/Tachyons CSS files.

  (My reading of projects like tachyons-styled-react, from the creator of Tachyons, is that critical-ness is still important goal/improvement even for static-utility-class approaches like Tachyons.)

• Psuedo-selectors/breakpoints go through Emotion/the CSS-in-JS framework, which is simpler, more powerful, and reduces method/abbreviation bloat.

  I.e. we don't need to suffix -nl for "not large" onto every single abbreviation.

• "Regular Emotion/CSS-in-JS" is easily/inherently available as an escape hatch for places where utility classes don't make sense.

  It's very likely you'll need "not utility" styles at some point in your project, and because Truss's DSL is already going through Emotion/CSS-in-JS anyway, it means your one-off "not utility" styles will use the same/consistent CSS-in-JS output/generation pipeline.

  This means you don't end up with mixed idioms of className="mx2 black" for 90% of your styles, but then "something different" like css={...} for the last 10%.

• Projects can easily tweak their preferred styles/abbreviations.

  Granted, this is very similar in spirit to Tailwinds customization, but for Truss, the config process is "just change some TypeScript code and run generate", and doesn't involve any changes to your build/webpack/PostCSS/etc. setup.

Why Tachyons Instead of Tailwinds?

tldr: Tachyon's abbreviations are shorter. :-)

For example, the CSS justify-content: flex-start in Tailwinds is justify-start, and in Truss is jcfs (i.e. the Justify Content Flex Start).

This is admittedly preference, but Truss's assertion is that readability goes up when code sprawl goes down, because you can visually fit more code into view at once.

And so Tachyons-style abbreviations, even if each abbreviation in isolation is more complex, when taken as a whole (looking at 10-20 lines of non-trivially-styled JSX) is arguably more readable.

Granted, the more-succinct code is still doing "the same work" (setting the same CSS properties) as the longer code, but you are likely only paying attention to a small subset of code at any given time, so the currently-unimportant code/abbreviations will "fade into the background" more easily when they're shorter.

(This is also not to say all names in a codebase should be meaningless chicken-scratch like a, b, c, etc., but when there are very strong/consistent conventions (like loop variables being called i, j, k), then leaning into succinctness can be appropriate.)

All this said, it's very possible to teach Truss how to generate Tailwinds-based abbreviations, we just haven't done it yet; see this issue if you're interested in helping contribute.

Themes

The word "theme" can mean either "static themes" (i.e. using the same consistent colors/fonts throughout your app, but the values themselves never really change) or "dynamic themes" (i.e. the user changing from light mode to dark mode).

For static themes, Truss's index.ts/palette.ts are specifically setup to centrally define your application's fonts, colors, etc. (see the "Configuration" section), so that they are consistently applied through your application.

For dynamic themes, Truss doesn't have any features dedicated explicitly to support them, but you can easily use CSS variables in your methods, i.e.:

const palette = {
  Primary: "var(--primary)",
  Secondary: "var(--secondary)",
};

And then have your application handle setting the --primary / --secondary values as appropriate (i.e. by importing a dark-mode.css or light-mode.css which define the respective CSS variable values).

Inspiration

Several libraries influenced Truss, specifically:

• Typed Tailwinds and babel-plugin-tailwind-components are both "type-safe TypeScript utility-css DSLs".

  In particular, the babel-plugin-tailwind-components insight of "if you just make csstype-compliant object literals, you can bring them to whatever CSS-in-JS framework you want" was a very useful/inspirational insight.

  The main difference between Truss and both Typed.tw and babel-plugin-tailwind-components is that Truss doesn't try to "perfectly match Tachyons or Tailwinds" (see "Why This Approach?"). Specifically, both projects assume that a tachyons.css or tailwinds.css file is the source-of-truth for your project's rules (and so parse/generate the TypeScript code from that CSS file); however, with Truss your source-of-truth is Truss's out-of-the-box TypeScript rules + whatever customizations you make in your project's truss/index.ts file (so rules are defined directly in TypeScript).

• Facebook's XStyles for the "typed extension" idea

Contributing

The Truss repository is set up as a Yarn workspace, although really the core package is just packages/truss, and the other packages are only for testing Truss with various output and various CSS-in-JS engines.

A basic development flow is:

• In the root directory, run yarn
• In the root directory, run yarn build -w
• Iterate as you want
• In the root directory, run yarn test to run all tests
  • Running individual tests in your IDE/each package should work as well
• In the root directory run yarn codegen to generate the testing Css.ts files

Todo

• npx -p @homebound/truss init type experience for setup - inspired by Storybook
• Support number[] increments as config
• Babel plugin that evaluates Css...$ expressions at build-time
  • I.e. see babel-plugin-tailwind-components and typed.tw's implementation
• Server-side generation; in theory this should just work?
• Add goober example