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

@empty123org/p1test

v1.0.5

Published

## API Typescript interface

Downloads

6

Vulnerabilities

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

Links

Git

Maintainers

stackchainstackchain

Keywords

Readme

Anzens/api

API Typescript interface

How to publish it to the NPM repository

Pre conditions

The file swagger.json MUST exist in the root folder of the project and it MUST contain a valid Swagger spec.

Releasing

Steps:
  1. Create a new branch with the version that you want to be based on the branch that is ready to production git checkout -b release/v1.0.0 main
  2. Push your new branch git push origin --follow-tags
  3. Prepare the version by running npx release-it --ci --increment (major|minor|patch|pre)
Results:
  1. It will bump the package.json version
  2. It will push the branch to your current upstream
  3. It will provide a link to create the release on the Github web interface. I.e 🔗 https://github.com/Emurgo/sc-services/releases/new?tag=v1.0.3&title=Release+1.0.3&body=*+chore%3A+release+it+%28a731ba2%29%0A*+Merge+pull+request+%231+from+stackchain%2F1.0.3-rc.1+%28e44a317%29%0A*+feature%28ci%29%3A+pipelines+%28b0f8e46%29&prerelease=false

When creating the release on Github web interface or via cli gh the option Pre-release MUST be checked, if the build version is tagged as beta, canary or rc, otherwise it will cause the Github workflow to fail when matching the version of the package.json against the release version. This will force having the appropriate package version on the NPM repository and on the Github.

The same rule above should be applied when creating a production version, the Pre-release options MUST NOT be checked.

The workflow will start the process of building and deploying it, only after the release is published (no longer set as a draft).

Post conditions

  • New tag with the new version
  • New branch tagged with the tag above
  • New release using the tag above

On success

On error

  • The workflow is red
  • The package was not published

Not covered

Hotfixes for old versions won't work with this pipeline. It will need to be published manually.

Merge the release

The branch created in this process won't be merged automatically.