CSSType

TypeScript and Flow definitions for CSS, generated by data from MDN. It provides autocompletion and type checking for CSS properties and values.

TypeScript

1import type * as CSS from 'csstype';
2
3const style: CSS.Properties = {
4  colour: 'white', // Type error on property
5  textAlign: 'middle', // Type error on value
6};

Flow

1// @flow strict
2import * as CSS from 'csstype';
3
4const style: CSS.Properties<> = {
5  colour: 'white', // Type error on property
6  textAlign: 'middle', // Type error on value
7};

Further examples below will be in TypeScript!

Getting started

1$ npm install csstype

Table of content

• Style types
• At-rule types
• Pseudo types
• Generics
• Usage
• What should I do when I get type errors?
• Version 3.0
• Contributing

Style types

Properties are categorized in different uses and in several technical variations to provide typings that suits as many as possible.

	Default	Hyphen	Fallback	HyphenFallback
All	Properties	PropertiesHyphen	PropertiesFallback	PropertiesHyphenFallback
Standard	StandardProperties	StandardPropertiesHyphen	StandardPropertiesFallback	StandardPropertiesHyphenFallback
Vendor	VendorProperties	VendorPropertiesHyphen	VendorPropertiesFallback	VendorPropertiesHyphenFallback
Obsolete	ObsoleteProperties	ObsoletePropertiesHyphen	ObsoletePropertiesFallback	ObsoletePropertiesHyphenFallback
Svg	SvgProperties	SvgPropertiesHyphen	SvgPropertiesFallback	SvgPropertiesHyphenFallback

Categories:

• All - Includes Standard, Vendor, Obsolete and Svg
• Standard - Current properties and extends subcategories StandardLonghand and StandardShorthand (e.g. StandardShorthandProperties)
• Vendor - Vendor prefixed properties and extends subcategories VendorLonghand and VendorShorthand (e.g. VendorShorthandProperties)
• Obsolete - Removed or deprecated properties
• Svg - SVG-specific properties

Variations:

• Default - JavaScript (camel) cased property names
• Hyphen - CSS (kebab) cased property names
• Fallback - Also accepts array of values e.g. string | string[]

At-rule types

At-rule interfaces with descriptors.

TypeScript: These will be found in the AtRule namespace, e.g. AtRule.Viewport.
Flow: These will be prefixed with AtRule$, e.g. AtRule$Viewport.

	Default	Hyphen	Fallback	HyphenFallback
@counter-style	CounterStyle	CounterStyleHyphen	CounterStyleFallback	CounterStyleHyphenFallback
@font-face	FontFace	FontFaceHyphen	FontFaceFallback	FontFaceHyphenFallback
@viewport	Viewport	ViewportHyphen	ViewportFallback	ViewportHyphenFallback

Pseudo types

String literals of pseudo classes and pseudo elements

• Pseudos

  Extends:

  • AdvancedPseudos

    Function-like pseudos e.g. :not(:first-child). The string literal contains the value excluding the parenthesis: :not. These are separated because they require an argument that results in infinite number of variations.

  • SimplePseudos

    Plain pseudos e.g. :hover that can only be one variation.

Generics

All interfaces has two optional generic argument to define length and time: CSS.Properties<TLength = string | 0, TTime = string>

• Length is the first generic parameter and defaults to string | 0 because 0 is the only length where the unit identifier is optional. You can specify this, e.g. string | number, for platforms and libraries that accepts any numeric value as length with a specific unit.

  1const style: CSS.Properties<string | number> = {
  2  width: 100,
  3};

• Time is the second generic argument and defaults to string. You can specify this, e.g. string | number, for platforms and libraries that accepts any numeric value as length with a specific unit.

  1const style: CSS.Properties<string | number, number> = {
  2  transitionDuration: 1000,
  3};

Usage

1import type * as CSS from 'csstype';
2
3const style: CSS.Properties = {
4  width: '10px',
5  margin: '1em',
6};

In some cases, like for CSS-in-JS libraries, an array of values is a way to provide fallback values in CSS. Using CSS.PropertiesFallback instead of CSS.Properties will add the possibility to use any property value as an array of values.

1import type * as CSS from 'csstype';
2
3const style: CSS.PropertiesFallback = {
4  display: ['-webkit-flex', 'flex'],
5  color: 'white',
6};

There's even string literals for pseudo selectors and elements.

1import type * as CSS from 'csstype';
2
3const pseudos: { [P in CSS.SimplePseudos]?: CSS.Properties } = {
4  ':hover': {
5    display: 'flex',
6  },
7};

Hyphen cased (kebab cased) properties are provided in CSS.PropertiesHyphen and CSS.PropertiesHyphenFallback. It's not not added by default in CSS.Properties. To allow both of them, you can simply extend with CSS.PropertiesHyphen or/and CSS.PropertiesHyphenFallback.

1import type * as CSS from 'csstype';
2
3interface Style extends CSS.Properties, CSS.PropertiesHyphen {}
4
5const style: Style = {
6  'flex-grow': 1,
7  'flex-shrink': 0,
8  'font-weight': 'normal',
9  backgroundColor: 'white',
10};

Adding type checked CSS properties to a HTMLElement.

1import type * as CSS from 'csstype';
2
3const style: CSS.Properties = {
4  color: 'red',
5  margin: '1em',
6};
7
8let button = document.createElement('button');
9
10Object.assign(button.style, style);

What should I do when I get type errors?

The goal is to have as perfect types as possible and we're trying to do our best. But with CSS Custom Properties, the CSS specification changing frequently and vendors implementing their own specifications with new releases sometimes causes type errors even if it should work. Here's some steps you could take to get it fixed:

If you're using CSS Custom Properties you can step directly to step 3.

1. First of all, make sure you're doing it right. A type error could also indicate that you're not :wink:

   • Some CSS specs that some vendors has implemented could have been officially rejected or haven't yet received any official acceptance and are therefor not included
   • If you're using TypeScript, type widening could be the reason you get Type 'string' is not assignable to... errors

2. Have a look in issues to see if an issue already has been filed. If not, create a new one. To help us out, please refer to any information you have found.

3. Fix the issue locally with TypeScript (Flow further down):

   • The recommended way is to use module augmentation. Here's a few examples:

     1// My css.d.ts file
     2import type * as CSS from 'csstype';
     3
     4declare module 'csstype' {
     5  interface Properties {
     6    // Add a missing property
     7    WebkitRocketLauncher?: string;
     8
     9    // Add a CSS Custom Property
     10    '--theme-color'?: 'black' | 'white';
     11
     12    // Allow namespaced CSS Custom Properties
     13    [index: `--theme-${string}`]: any;
     14    
     15    // Allow any CSS Custom Properties
     16    [index: `--${string}`]: any;
     17
     18    // ...or allow any other property
     19    [index: string]: any;
     20  }
     21}

   • The alternative way is to use type assertion. Here's a few examples:

     1const style: CSS.Properties = {
     2  // Add a missing property
     3  ['WebkitRocketLauncher' as any]: 'launching',
     4
     5  // Add a CSS Custom Property
     6  ['--theme-color' as any]: 'black',
     7};

   Fix the issue locally with Flow:

   • Use type assertion. Here's a few examples:

     1const style: $Exact<CSS.Properties<*>> = {
     2  // Add a missing property
     3  [('WebkitRocketLauncher': any)]: 'launching',
     4
     5  // Add a CSS Custom Property
     6  [('--theme-color': any)]: 'black',
     7};

Version 3.0

• All property types are exposed with namespace
  TypeScript: Property.AlignContent (was AlignContentProperty before)
  Flow: Property$AlignContent
• All at-rules are exposed with namespace
  TypeScript: AtRule.FontFace (was FontFace before)
  Flow: AtRule$FontFace
• Data types are NOT exposed
  E.g. Color and Box. Because the generation of data types may suddenly be removed or renamed.
• TypeScript hack for autocompletion
  Uses (string & {}) for literal string unions and (number & {}) for literal number unions (related issue). Utilize PropertyValue<T> to unpack types from e.g. (string & {}) to string.
• New generic for time
  Read more on the "Generics" section.
• Flow types improvements
  Flow Strict enabled and exact types are used.

Contributing

Never modify index.d.ts and index.js.flow directly. They are generated automatically and committed so that we can easily follow any change it results in. Therefor it's important that you run $ git config merge.ours.driver true after you've forked and cloned. That setting prevents merge conflicts when doing rebase.

Commands

• npm run build Generates typings and type checks them
• npm run watch Runs build on each save
• npm run test Runs the tests
• npm run lazy Type checks, lints and formats everything