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

solar-manager-device-statistics-trigger

v1.1.3

Published

### Using semantic-release semantic-release automates the package release workflow including: determining the next version number, generating the release notes, and publishing the package. This removes the immediate connection between human emotions and v

Downloads

3

Vulnerabilities

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

Links

Maintainers

pavlo.ilchukpavlo.ilchuk

Keywords

Readme

CI/CD

Using semantic-release

semantic-release automates the package release workflow including: determining the next version number, generating the release notes, and publishing the package. This removes the immediate connection between human emotions and version numbers, strictly following the Semantic Versioning Specification and communicating the impact of changes to consumers.

MAJOR.MINOR.PATCH version numbering

Increment the:

  • MAJOR version when making incompatible API changes,
  • MINOR version when adding functionality in a backward compatible manner,
  • PATCH version when making backward compatible bug fixes.

Rules for committing to development branch

| commit | release | next version | sample commit message | |-----------|---------|--------------|-----------------------------------------------------| | refactor: | patch | 1.0.0->1.0.1 | refactor: implement calculation method as recursion | | fix: | patch | 1.0.0->1.0.1 | fix: add missing parameter to service call | | docs: | patch | 1.0.0->1.0.1 | docs: update readme | | style: | patch | 1.0.0->1.0.1 | style: update readme | | test: | patch | 1.0.0->1.0.1 | test: update unit tes | | build: | major | 1.0.0->2.0.0 | build: upated look file | | ci | patch | 1.0.0->1.0.1 | ci: add new stage (integration test) | | revert | patch | 1.0.0->1.0.1 | revert: revert to commit | | feat: | minor | 1.0.0->1.1.0 | feat(lang): add Polish language | | chore: | minor | 1.0.0->1.1.0 | chore: drop support for Node 6 | | perf: | minor | 1.0.0->1.1.0 | perf: -//- |

Conventional Commits

  • The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top of. This convention dovetails with SemVer, by describing the features, fixes, and breaking changes made in commit messages.

  • The commit message should be structured as follows:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

  • The commit contains the following structural elements, to communicate intent to the consumers of your library:

  1. fix: a commit of the type fix patches a bug in your codebase (this correlates with PATCH in Semantic Versioning).

  2. feat: a commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in Semantic Versioning).

  3. BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE can be part of commits of any type.

  4. types other than fix: and feat: are allowed, for example @commitlint/config-conventional (based on the Angular convention) recommends build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others.

https://www.conventionalcommits.org/en/v1.0.0/