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

@wishlist/types

v4.0.21

Published

Types for wishlist app

Downloads

4

Readme

Types for wishlist app

Step 1:

Once your feature-branch is merged into master create new branch from master: git pull origin master git checkout -b release-types-v1.2.3

Step 2: Generate the new version running, depending on the changes you did: npm version [patch|minor|major]

Step 3: Commit the changes made in the package.json and package-lock.json and push the changes to Github.

Step 4: Create a Pull request, once it's approved merge it into master.

Step 5: Switch back to master and pull the changes: git checkout master git pull origin master

Step 6: Generate a tag for the release, the structure should be the folder name [ api | sdk | migrations ] followed by @ and the version generated on Step 2: git tag -a [email protected] -m "add comment here"

Step 7 (Integration): Push the changes to master, will deploy it to Integration: git push origin master

Step 8 (Staging): By pushing the changes to the tag (i.e. [email protected]) will trigger the deploy into staging: git push origin [email protected]