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

@statistikzh/leu

v0.11.0

Published

UI component library of the canton of zurich

Downloads

22

Readme

🦁 leu

A UI component library based on the design system of the canton of zurich.

⚠️ This project is still in alpha state

This package is still in alpha state. It is not recommended to use it in production yet.

Prerequisites

Node.js > v18.0.0

Installation

npm i @statistikzh/leu

Usage

In order for the components to work, you need to load the theme styles and the font definitions globally. The theme file is part of the package (dist/theme.css). The fonts on the other hand have to be licensed and are therefore not included in the package.

If you have an environment that resolves bare module imports, you can use the library like this:

<link rel="stylesheet" href="@statistikzh/leu/theme.css" />
<script type="module">
  import "@statistikzh/leu/leu-input.js"
</script>

<leu-input></leu-input>

CDN

Browsers can't resolve bare module imports without import maps. But we can use a CDN to resolve the imports for us. This is useful if you're just using plain HTML and JavaScript without any build or transformation steps. Also this is applicable in an environment like Observable.

<link
  rel="stylesheet"
  href="https://esm.run/@statistikzh/[email protected]/dist/theme.css"
/>
<script type="module">
  import "https://esm.run/@statistikzh/[email protected]/dist/leu-input.js"
</script>

<leu-input></leu-input>

Linting and formatting

To scan the project for linting and formatting errors, run

npm run lint

To automatically fix linting and formatting errors, run

npm run format

Testing with Web Test Runner

To execute a single test run:

npm run test

To run the tests in interactive watch mode run:

npm run test:watch

Demoing with Storybook

To run a local instance of Storybook for your component, run

npm run storybook

To build a production version of Storybook, run

npm run storybook:build

Create a new component

To create a starting point for a new component, run

./scripts/generate-component/generate.js

Running it with --help will show you all available options.

Development guidelines

A few rules are necessary when developing a component library. The following conventions and guidelines should be followed when new features are implemented.

At the same time they're not set in stone. If the there is a good reason to change them open a pull request.

Naming

Every element, class or custom property that will be globally available has to be prefixed with leu.

/* Custom elements */
class LeuRadio extends LitElement {
  ...
}

window.customElements.define("leu-input", LeuInput)
/* CSS class */
.leu-radio-group {
  ...;
}

/* CSS custom property */
:root {
  --leu-color-black-0: #000;
}

Scoped styles

All CSS declarations should, whenever possible, always live inside a custom element. This way we ensure that the styles won't interfere with the environment they're loaded into. The only exceptions are @font-face statements and custom property declarations. Styles that are shared between components should be defined as global custom properties inside the styles/custom-properties.css. When a global custom property is used inside a component it should always be assigned to a local custom property in the :host declaration block.

:host {
  --radio-color-disabled: var(--leu-color-black-20);
}

Value property

All custom elements that contain a value of some sort have to implement a value property. Everytime the value of the value property changes a input event has to be dispatched. This behaviour matches the way Observable handles and observes changes of values that are contained in arbitrary elements. We decided to take over this pattern as it is usable in every other environment too.

Custom events

In case of a custom event that is meant to be catched by an other component of this library, the name of this event has to be prefixed too.

this.dispatchEvent(new Event("leu:select", { bubbles: true, composed: true }))

Dependencies

Use as little dependencies as possible and as many as needed.

Contributors

Thanks to the following people who have contributed to this project

@cubmic @resmartiZH @daenub

Contact

Dan Büschlen [email protected]

Twitter Follow

License

This project uses the following license:

Guidelines for contributing

We welcome contributions. Please see our CONTRIBUTING.md file for detailed guidelines of how to contribute.

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.