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

@antoniogiroz/pkg-changesets

v0.2.1

Published

Package creation using changesets to manage the releases

Downloads

3

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

antoniogirozantoniogiroz

Keywords

Readme

pkg-changesets

Package creation using changesets to manage the releases

How to work with this way of creating packages

  1. Create a branch
  2. Make changes
  3. Commit changes and push the branch
  4. Once all changes are done, run pnpm changeset to create a changeset specifying the changes you made *
  5. Create a PR
  6. Merge the PR

Do the previous steps for each change you want in the next release.

  • You also can commit to the main branch if it's not protected, but you will have to create a PR with all the changesets, running the command pnpm changeset for each change you have made.

How to create a release

  1. Each time you have executed the pnpm changeset command, you generate a new file in the .changeset folder. This file contains the changes you made and the version you want to release. You can edit this file to change the version you want to release.

  2. When some files inside the .changeset folder are detected in the main branch, a new Pull Request is created, where the changes are summarized in the CHANGELOG.md and the version is updated. This PR is created by the changeset-bot user.

  3. Once the PR is merged, the changes are published to npm and the release is created in GitHub.