The design system is published on NPM and can be installed as a package. It also has a peer dependency on lit so you need to install that as well. This is so to prevent conflicting version of lit being used in the same application, and leaves the choice of which version of lit to use to you.

npm install @lansforsakringar/core-components lit

You then need to import the components in your application for them to be available.

import '@lansforsakringar/core-components'

Styles

You'll also need to import the global styles in your application. This includes the global CSS variables and fonts. If you are using build tools like Vite or Webpack, you can import the CSS file directly in your JavaScript.

import '@lansforsakringar/core-components/index.css'

Or in your CSS if you are using a CSS preprocessor like PostCSS.

@import '@lansforsakringar/core-components';

If you are not using a build tool, you can either load the styles from a CDN, see Script/Link Tag, or copy the neccessary files and serve them yourself, see CLI.

React

The design system includes a React build that can be used to render the components in a React application. To use the React components you also need to install the @lit/react peer dependency.

npm install @lansforsakringar/core-components lit @lit/react

import { LfuiButton } from '@lansforsakringar/core-components/react'

export default function App() {
  return (
    <LfuiButton onLfClick={() => console.log('clicked')}>Click me</LfuiButton>
  )
}

Bundler plugins

For convenience, the design system provides plugins for popular bundlers that can be used to serve these assets.

Vite

The design system provides a Vite plugin that will copy the assets to the provided assetDir relative to the Vite out directory, or during development serve them as if they were local files in the public folder.

// vite.config.js
import { lfui } from '@lansforsakringar/core-components/vite'

export default {
  plugins: [lfui({ assetDir: 'lfui-assets' })]
}

Webpack

The design system also provides a Webpack plugin that will copy the assets to the provided assetDir relative to the Webpack output directory, or during development serve them as if they were local asset resources.

// webpack.config.js
const LFUIPlugin = require('@lansforsakringar/core-components/webpack')

module.exports = {
  plugins: [new LFUIPlugin({ assetDir: 'lfui-assets' })]
}

On build, the assets will be copied over to the provided assetDir relative to the Vite out directory.

Selfhosted

If you are not using a bundler or want to serve the assets in a different way, you can copy them to your web server and serve them yourself, see CLI.

CLI

This packages comes with a CLI for common tasks like exporting assets.

Export

The export command will take all JS/CSS entry points, including their associated dependencies and assets, and copies them to a directory of your choice.

$ lfui export --out dist/lfui

Assuming that the "dist" folder is publicly accessible on your server, you can reference the files like this in your application:

<!doctype html>
<html>
  <head>
    <script type="module" src="/lfui/main.js"></script>
    <link rel="stylesheet" href="/lfui/main.css" />
  </head>
  <body>
    <lfui-button>Click me</lfui-button>
  </body>
</html>

Keywords

FAQs

What is @lansforsakringar/core-components?

Is @lansforsakringar/core-components popular?

Is @lansforsakringar/core-components well maintained?

Package last updated on 25 Aug 2025

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

@lansforsakringar/core-components

LFDS Core Components

Using Components

Bundling