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

tup-js

v0.0.1

Published

ThredUP JavaScript packages

Downloads

6

Readme

tup-js

ThredUP JavaScript Packages

About

This is intended to be a monorepo of small, independantly versioned packages that are shared across applications.

Lerna is used to attempt to optimize this workflow.

Getting Started

Install and link dependencies:

npm run bootstrap

Adding a new package

  • Add a new directory for the package under packages
  • Follow common directory conventions:
    • src - all the source code for the package
    • dist - build output
    • test - unit tests
  • Provde common npm scripts:
    • lint - eslint rules are pre-configured at the project root
    • test - run unit tests
    • test-ci - run unit tests with code coverage and output test resuls in JUnit format for CI
    • clean - delete build artifacts
    • cover - code coverage
    • cover:check - check if code coverage is within tolerance
    • build - run babel compilation, if required
    • prepare - run lint, test, clean, and build

Commit messages

Please use convential commits to help communicate the nature of changes, generate the changelog and for determining the version bump.

Publishing a package

  • Get your PR reviewed/merged

  • Locally update your master branch git pull origin master

  • Publish new version of the packages to npm

    • without 2FA enabled
    npm run publish
    • with 2FA enabled

    If your npm login has 2FA enabled, use your authenticator app to get a 2FA code and set as an environment variable:

    NPM_CONFIG_OTP=12345 npm run publish
  • Push your local master branch to origin git push origin master

Other commands

Run tests for all packages

npm test

Run linter for all packages

npm run lint

Run code coverage for all packages

npm run cover

Remove node_modules for all packages

npm run clean

Build all packages

npm run build