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

@proprioo/salatim

v35.6.0

Published

Proprioo component library

Downloads

1,537

Readme

Salatim

Salatim is our component library, made with 🥑 and ❤️.

Please have a look on its storybook for each components.

Before

Don't forget to add an empty NPM_TOKEN in your bash_profile, zsh, etc.. and reload it.

export NPM_TOKEN=''

Status

build status

| Branches | Functions | Lines | Statements | | :-------------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------ | | branches coverage | functions coverage | lines coverage | statements coverage |

Pages

Source Map Explorer

Storybook

How to dev ?

Use yarn dev

How to build ?

Use yarn build

Update version

Before each change, please update CHANGELOG.md with a new version using the following template:

**major.minor.patch**

    * Commit message

    OR

    **BREAKING CHANGE** Commit message
  • Fix: patch
  • Component / Feature: minor
  • Everything which can bring changes in the different projects: major

When changelog is updated, don't forget to bump the package.json version with:

$ yarn version --major | --minor | --patch

Release new version

Pushing a new version in the master branch automatically trigger a new release of the NPM package.

Backport a fix

If you have to backport something to an old version of salatim :

  1. go to the old version's branch (for example: v15 before the rebranding)
  2. add your commit(s), and don't forget to bump the version in package.json and CHANGELOG.md (if you fix something and the previous version was 15.2.3, bump to 15.2.4)
  3. push the branch, don't forget it!
  4. run yarn clean && yarn build locally to make the package ready to be published
  5. run yarn publish --access=public --non-interactive --tag 15.2.4 locally. Don't forget the --tag argument to prevent overriding the latest version.

You can then bump your project with this new version of salatim. ;)