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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@cas-smartdesign/styles

v3.8.0

Published

A shared package providing style variables and basic style sheets to create SmartDesign like components and apps.

Readme

@cas-smartdesign/styles

A shared package providing style variables and basic style sheets to create SmartDesign like components and apps.

Entry points and bundles

The package has two main SCSS files and two corresponding CSS bundles.

  • scss/styles.scss (compiled to dist/styles.css)
  • scss/theme.scss (compiled to dist/theme.css)

Styles bundle

Contains prefixed class rules that can be added to your components to make them fit into SmartDesign.

In order to make use of the predefined variables (e.g. colors or spacings) in your components we recommend to use the styles.scss file or the module SCSS files and include it in your build process.

Theme bundle

The theme bundle contains every rule that is contained in the styles and also defines rules to some standard HTML tags that makes it easier to style a simple page.

Note that as it can modify the look and feel of other components we don't recommend this to be used on complex apps that also use third party elements.

SCSS structure

Beside the main files every SCSS file is declared as partial and they are organized in two folders:

Variables (scss/variables)

Files in this folder contain shared variables that are used for components or other modules.

Modules (scss/modules)

Files in this folder contain rules that are specific for a topic or component.

| Module | Description | | :---------: | ---------------------------------------------------------------------- | | app | Defines the most basic styles | | base_colors | Defines auto generated classed to change the color of a single element | | button | Defines rules for button-like elements | | colors | Defines classes for SmartDesign specific colors (mostly backgrounds) | | link | Defines rules for hyperlink-like elements | | misc | Defines rules for the simplest components | | spacing | Defines classes for setting pre-defined margin and padding values | | typography | Defines classes for setting pre-defined typography values |

Styling guidelines

  • Every rule should behave the same in all the supported browsers
  • Always use the "sd-" prefix for class names
  • Beside the theme bundle, avoid changing default HTML styles
  • Only use !important keyword for very specific rules (e.g. sd-hidden, sd-red)
  • A variable file must not reference to files outside the variables folder (e.g. the modules folder)
  • A module file can use other modules and variables, but dependencies should be imported explicitly