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

@salable/gds

v2.3.3

Published

Global Design System (GDS) build for the Salable application. Maintained by the Salable team.

Downloads

28

Readme

CI Checks  License Checker  Release 

Salable-GDS

This monorepository contains all of the core Salable components, known as the Salable Global Design System (Abbreviated to Salable GDS or just GDS).

Getting Started

In this section is everything you need to do and know about to get the Salable GDS up and running on your local machine.

Prerequisites

Before starting the setup of the Salable GDS on your local machine, there are a few housekeeping tasks that need to be sorted first.

NOTE: This README has been written from the perspective of a macOS user, if you are configuring this on a different OS such as Windows or Linux then you will likely need to find/use equivalents for things like Brew and folder directories like root (~) (windows).

Node/NPM

As with most projects nowadays we need Node and NPM installed on our machine for the app to run. I won't go into the details of installing Node.js here but instead will refer you to using NVM to install Node

At the time of writing we don't have an agreed-upon version of Node to run but as a rule of thumb, for now, install Node LTS or higher.

TODO: Update the above statement once we have an agreed version of Node and everyone is using it. Then bump accordingly as we update.

Repo Setup

To get started with configuring the repo locally, clone it from GitHub to a location of your choosing on your machine. Once the clone is complete, open the directory in your favourite IDE.

Installing Dependencies

Now we are ready to install packages and get the app up and running. 🙌

First of all, we need to run npm install in the root directory to install all of the dependencies for all of the depdencdencies

The Salable GDS should now be installed and ready to go. 🎉

Running Salable GDS Locally

Everything you need to know about running the Salable GDS locally from your first time to your nth time.

Initial Setup

To run the Salable GDS locally, you will need one terminal window open.

In the terminal window, run the command npm run storybook in the salable-gds folder to start the development server. At this point, a new browser window should open to http://localhost:6006/.

You will now have access to the Salable GDS.

Conventions

NOTE: commits to this repository must follow the Conventional Commits git commit specification, this is handled automatically by the npm run commit script

  • The repository implements commitizen for conventional commits
  • The npm run commit command must be run in order to create a commit first