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

@union/ts-components

v1.1.21

Published

[![Build Status](https://travis-ci.org/unionco/ts-components.svg?branch=master)](https://travis-ci.org/unionco/ts-components)

Downloads

18

Readme

Union Styled Components Library w/Typescript [WIP]

Build Status

Getting Started

Simply run the commands below and you should have a working storybook displaying all of our components.

  • git clone repo
  • yarn install
  • yarn dev

Adding Components

Each component follows the folder structure below:

  • ComponentName
    • index.tsx
    • index.stories.tsx
    • styles.ts

Index.tsx

Exports react component to be consumed

Stories.tsx

Showcase of component for storybook

Styles.ts

Exports a styled component consumed by the react component

Publishing to NPM

When you are ready to publish the package to NPM, use the release.prepare script:

yarn run release.prepare -m "Commit message" --patch

This script will increment the version number in package.json based on the specified version type (--patch, --minor, or --major are valid switches). The script will also check in the changes, commit the changes, and create a git tag with the new version number.

After the script runs successfully, you will need to push the tag to Github. Once the tag is pushed, Travis CI will run and publish the package to NPM. This process usually takes 1-2 minutes.

git push origin x.y.z

Where x.y.z is the new version number (part of the script output).

Notes:

  • If the git commit message is left blank, it will default to "[Release]"
  • If the version type is left blank, patch will be used by default

Travis CI

https://travis-ci.org/unionco/ts-components

Travis CI runs only when tags are pushed! master/branch commits will not trigger a deploy to NPM.