Getting started for developers

This page describes how to get started building a web application with Warp styling and components. Warp is using UnoCSS, an atomic CSS engine. UnoCSS works by searching for the utilities (classes) usages from your codebase and generate the corresponding CSS on-demand. The Warp preset contains the utilities UnoCSS will look for. Only the used utilities are shipped to your app, ensuring speed and efficiency in any project size.

If you are migrating from Fabric to Warp, please visit the Migration page.

If you have any questions or need clarification, please don't hesitate to reach out to the Warp team on the #nmp-warp-design-system channel on Slack!

1. Integrate with UnoCSS and Warp

A guide on how to integrate your project with UnoCSS and Warp.

Build time

Installation

To get started, you need to install the necessary packages.

npm install unocss @warp-ds/uno @warp-ds/css

If you are using Webpack

In addition to the installation of the Warp packages, Webpack based projects should also install @unocss/webpack

npm install @unocss/webpack --save-dev

See UnoCSS docs for more information.

---

Configuration and setup

When setting up Warp in your project, you can choose to create a uno.config.js file, or you can include the UnoCSS configuration settings directly in the build tool. Below, the two different alternatives are described.

Alternative 1

• Add a uno.config.js file

  Create a uno.config.[js,ts,mjs,mts] file with the following content. This file will configure UnoCSS with our Warp preset.

  uno.config.js

  import { defineConfig } from 'unocss';
  import { presetWarp } from '@warp-ds/uno';
  import { classes } from '@warp-ds/css/component-classes/classes';
  
  export default defineConfig({
    presets: [presetWarp({ externalClasses: classes, skipResets: true })],
  });

  By default, UnoCSS will automatically look in the root directory of your project for uno.config.[js,ts,mjs,mts] or unocss.config.[js,ts,mjs,mts].

  Details about this configuration setup

  When an application consists of several parts (e.g. if you are using [Podium](https://podium-lib.io/)) and each part needs to integrate with UnoCSS and Warp - it's more performant to get styling from an external stylesheet (as this will be cached in the browser) instead of making UnoCSS generate the same CSS multiple times. In the example above we pass external classes and skip resets, because we import components.css and reset.css as mentioned [below](/getting-started/developers/#make-sure-you-import-the-resets-and-components-classes-from-eik-cdn).

  See all configuration options for presetWarp at https://github.com/warp-ds/drive#plugin-api.

• Add UnoCSS to your build tool

  Then add UnoCSS to your build tool. Below is an example for Vite, but you choose whatever build tool that suites your case. For more examples how to configure other building tools, please refer to the examples found in the UnoCSS project. We will eventually have in-depth installation guides for frameworks on the golden path.

vite.config.js

import { defineConfig } from 'vite';
import UnoCSS from 'unocss/vite';

export default defineConfig({
  plugins: [UnoCSS()],
});

Alternative 2

• Include UnoCSS directly in the build setup

  You can also specify the configuration file manually and in that case you won't need a separate uno.config.js file.

  Below is an example for Vite:

  vite.config.js

  import { defineConfig } from 'vite';
  import UnoCSS from 'unocss/vite';
  import { presetWarp } from '@warp-ds/uno';
  import { classes } from '@warp-ds/css/component-classes/classes';
  
  export default defineConfig({
    plugins: [
      UnoCSS({
        presets: [presetWarp({ externalClasses: classes, skipResets: true })],
      }),
    ],
  });

• Add uno.css to your main entry

  Depending on the build tool you have chosen, this step can look different. The example below is applicable if you build UnoCSS together with Vite. If you for example use PostCSS as a build tool, you would need to add @unocss to the main stylesheet. Please take a look at the examples and see what is needed to be added in your setup.

  e.g. main.js or main.ts

  import 'uno.css';

---

Runtime

UnoCSS also provides a CSS-in-JS runtime module which runs the UnoCSS engine right in the browser. It will detect the DOM changes and generate the styles on the fly. See "Runtime" section of UnoCSS docs for more information and examples.

Bundler usage

npm install @unocss/runtime @warp-ds/uno

import initUnocssRuntime from '@unocss/runtime';
import { presetWarp } from '@warp-ds/uno';

window.__unocss = {
  presets: [presetWarp()],
};

initUnocssRuntime();

---

UnoCSS CLI

With the custom configurations in uno.config.js, you can also generate styles at build step using UnoCSS's standalone client. See UnoCSS CLI for more information and examples.

---

Use with Shadow DOM and Vite

In case of apps using Vite where Warp components are used inside Shadow DOM, the css generated by the UnoCSS plugin needs to be inlined into the Shadow DOM style. See UnoCSS Vite plugin's shadow-dom mode for more information.

2. Apply theme

Add fonts

In order to load correct fonts for each brand, you need to include a font setup for that brand in your document.

Add this to your index.html:

<link
  rel="stylesheet"
  href="https://assets.finn.no/pkg/@warp-ds/fonts/v1/finn-no.css"
/>

Add brand CSS

In order to apply your application's theme, a respective brand CSS should be added to the document. Brand specific stylesheets are available via our Eik CDN server:

• Finn: https://assets.finn.no/pkg/@warp-ds/css/v1/tokens/finn-no.css
• Tori: https://assets.finn.no/pkg/@warp-ds/css/v1/tokens/tori-fi.css

Add this to your index.html:

<link
  rel="stylesheet"
  href="https://assets.finn.no/pkg/@warp-ds/css/v1/tokens/finn-no.css"
/>

Make sure you import the resets and components classes from Eik CDN:

<link
  rel="stylesheet"
  href="https://assets.finn.no/pkg/@warp-ds/css/v1/resets.css"
/>
<link
  rel="stylesheet"
  href="https://assets.finn.no/pkg/@warp-ds/css/v1/components.css"
/>

3. Use Warp components

Select which Warp component library you wish to set up:

Installation

The Warp React package can be installed from NPM.

npm install @warp-ds/react

Setup

Since warp components are internationalised, you'd need to either set NMP_LANGUAGE for server-side rendering of the component, or set html document lang with a two-letter-code, eg: <html lang="en">. The server-side variable is read as process.env.NMP_LANGUAGE so you could either define this in your package.json script, or use .env files to leverage dotenv.

Using Components

Once installed, components can be imported into your app by name.

import { Box } from '@warp-ds/react';

You can also import them individually to optimize your JS bundle size by adding only the components you need:

import { Box } from '@warp-ds/react/components/box'

You can find the specific import statement to import each component on that component's documentation page. For example, here's the button page

TypeScript support

The components are written in TypeScript. To take advantage of this, make sure your project is up to date on the latest @types/react definitions.

npm install @types/react --save-dev

Eik support

We publish @warp-ds/react package to EIK cdn in 2 variants, eg:

For react 18:

https://assets.finn.no/pkg/@warp-ds/react/v1/warp-react-18.js

For react 17:

https://assets.finn.no/pkg/@warp-ds/react/v1/warp-react-17.js

Import mapping

We publish a Warp import map for use with Eik. Be sure to include the React import map first.

{
	"name": "my-app",
	"version": "1.0.0",
	"server": "https://assets.finn.no",
	"import-map": [
		"https://assets.finn.no/map/react/v18",
		"https://assets.finn.no/map/warp/v2"
	]
}

Legacy React v17 support

While we no longer officially support React v17, in order to buy yourself time to migrate to React v18, you can add the Warp legacy map for interrim support. When React v19 is released, React v17 support will be dropped entirely. Map order is important.

{
	"name": "my-app",
	"version": "1.0.0",
	"server": "https://assets.finn.no",
	"import-map": [
		"https://assets.finn.no/map/react/v17",
		"https://assets.finn.no/map/warp/v2",
		"https://assets.finn.no/map/warp-legacy/v2"
	]
}