npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@sikt/sds-tokens

v2.1.0

Published

## Consume

Downloads

27,385

Readme

@sikt/sds-tokens

Consume

npm i -s @sikt/sds-tokens

Stylesheet

@import url("@sikt/sds-tokens");

.prefix-custom-block__element--blue {
  color: var(--sds-color-brand-primary-strong);
}

Note CSS tokens are best used by importing @sikt/sds-core which will include them as CSS variables. But you can still make use of them directly from @sikt/sds-tokens if need be.

React

import * as tokens from "@sikt/sds-tokens";

<Button style={{ color: tokens.default.color.brand.primary.strong.value }}>
  Hello, World!
</Button>;

Sassy CSS

@use "@sikt/sds-tokens/scss/tokens";

.prefix-custom-block__element--blue {
  color: tokens.$sds-color-brand-primary-strong;
}

Note SCSS tokens are currently only for showcase and will need a little love by the first one making use of them.

Design Tokens

Colors are available in light (default) and dark scheme.
Sizes are, in some cases, available for media mobile (default), tablet & desktop.
When there is no corresponding token in the non-default version the default should be used.

Tips

  • Relative size tokens (--sds-base-size-relative-<size>) should be used on user font size setting scalable properties like font-size, line-height, etc. These are calculated from the root font-size so that for example 16px is the same as calc(16 * 1rem / 16).
  • Custom media queries are transformed to valid CSS during build step and need to be imported into the PostCSS file that uses them.

Note There is currently a bug in Figma that translates HSL to incorrect HEX color values. If you use the same name token you will get the correct HEX color value.

Contribute

Created using Style Dictionary and exported as CSS, SCSS & JavaScript variables.

Note Do not edit these directly in the /dist output directory but rather in the /src source directory.

Note Style Dictionary tokens follow a CTI (Category/Type/Item) naming pattern that may affect their outcome by what transforms are applied.

TODO: SCSS media query mixins.
TODO: JavaScript relative size variables. How are these used in non-CSS environments?