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

@soulmonk-dev/test-auto-release-npm-package

v0.3.0

Published

Using git actions, release npm package and create release note

Downloads

3

Readme

test-auto-release-npm-package

How to implement

  • copy .github/workflows/npm-publish.yml to your project, made some adjustments, if necessary
    • dependency on test
    • remove test flow if you have separate CI/CD for testing (with complicated)
  • set up secret for project NPM_TOKEN
  • every time you push a new tag it will create a new publishing

Flow

Manual / automatic

  • do tasks
  • before release create pr:
    • easy way npm version minor --no-git-tag-version with bumping
  • after merge bump release, trigger git action by running
    npm run create-tag
    it should switch to main, create tag based on version in package json and push it
  • wait and check create release after git action done )

To do it Automatic

Note: Not all changes in the main branch can be triggered as a new publication

Update npm-publish.yml flow on: push: branches: [ main ]

and then:

  • open pr
  • do not forget before marge to run npm version minor

Q&A

Cannot get access to private repository

npm publish --access public

TODO

npm version minor --no-git-tag-version && git push --tags $(grep -m1 version package.json | awk -F: '{ print $2 }' | sed 's/[", ]//g')

Links

  • Good example of workflows: https://github.com/MylesBorins/node-osc/tree/main/.github/workflows
  • https://stedolan.github.io/jq