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/js-sdk

v2.0.0

Published

## Packages Included

Downloads

8

Readme

@salable/js-sdk

Packages Included

Development

Initial Setup

To set up the JS SDK on your local machine for development, perform the following steps.

  1. Clone the repo to your local machine
  2. Run npm i at the root of the project

Note: You don't need to run npm i per package. Because this project uses NPM workspaces, you only ever need to run it at root.

Adding Packages

If you want to add a new package, perform the following steps.

  1. Create a new folder inside the packages directory named as the name of the package. (e.g. pricing-table)
  2. Inside the new package folder, create package.json and README.md files.
    • Use the template for package.json below, replacing information where required.
  3. Create a src folder in the root of your new package folder and inside it put a index.ts or index.js file depending on if you're using TS or not.
    • From the index.{js|ts} file, export your package's files. This file is the entry point for Rollup to build from.
  4. Update ./packages/index.ts to include your new package index file to ensure it is included in the output build.
    • Export your new package from ./packages/index.ts with a name based on your package name.
  5. Update this README.md file to include your new package in the list of packages at the top fo this file.
  6. To install/uninstall NPM packages to your new package, use the following commands and replace information where required. NOTE: For your package name, use the directory name inside ./packages
    • Install: npm install <NPM_PACKAGE_NAME> -w <YOUR_PACKAGE_NAME>
    • Uninstall: npm uninstall <NPM_PACKAGE_NAME> -w <YOUR_PACKAGE_NAME>

package.json example

{
  "name": "@salable/<YOUR_PACKAGE_NAME>",
  "version": "1.0.0",
  "description": "",
  "type": "module",
  "main": "src/index.{js|ts}",
  "scripts": {
    // Your scripts here
  },
  "author": "Salable",
  "license": "MIT"
}

Example

For an example package, see the pricing-table package/directory inside ./packages.