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

liber-salti

v2.53.0

Published

Saltí - Liber Design System

Downloads

45

Readme

Saltí

Commitizen friendly

Liber Design System. This project was created using:

It also features:

Usage

Package

You can use this package adding it to your project with the command:

yarn add liber-salti

⚠️ Be aware of the peer dependencies of this library.

Examples

You can check each component's example in out Storybook page.

Development

Linting

yarn lint

Automatic fix errors:

yarn lint --fix

Testing

yarn test

Obs: we are currently using Storyshots for snapshot testing the Storybook stories.

If they fail with your change, analyze if this change should be affecting another stories or not. If so, you can update them by running:

yarn test -u

Building

yarn build

Storybook

To run a live-reload Storybook server on your local machine:

yarn storybook

To export your Storybook as static files:

yarn storybook:export

You can then serve the files under storybook-static.

Generating New Components

There is a NodeJS util file under util called create-component.js. Instead of copy pasting components to create a new component, you can instead run this command to generate all the files you need to start building out a new component. To use it:

yarn generate YourComponentName

This will generate:

/src
  /YourComponentName
    YourComponentName.tsx
    YourComponentName.stories.tsx
    YourComponentName.test.tsx
    YourComponentName.types.ts
    YourComponentName.styles.ts
    index.ts

The default templates for each file can be modified under util/templates.

Installing Component Library Locally

Let's say you have another project (test-app) on your machine that you want to try installing the component library into without having to first publish the component library. In the test-app directory, you can run:

yarn add ../salti

Which will install the local component library as a dependency in test-app. It'll then appear as a dependency in package.json like:

  ...
  "dependencies": {
    ...
    "salti": "../salti",
    ...
  },
  ...

Your components can then be imported and used in that project.

⚠️ You might have to delete this project's node_modules folder before installing it locally in another app, so the lib uses the other project's packages, avoiding errors like "duplicate React found" or so.

Publishing

NPM and semantic-release

This project is configured with GH Actions workflows for setting a new release using semantic-release and publishing it on NPM Registry.