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

semantiq

v0.0.3

Published

Gets the version number of the next release

Downloads

2

Readme

Semantiq

A most basic cli that gets the next semantic release, looking at the last commit and package.json version.

code style: prettier Build Status codecov GitHub npm


Contents

Usage

Install

npm install semantiq

CLI

semantiq

Expected output is the next release if the last commit follows the Angular commits convention and a package.json exists.

Example

Given you have a commit of:

feat: My brand new feature!

And a package with:

{
    "version": "1.0.1"
}

When you call semantiq, the result will be:

$ 1.1.0

Commit Flags 🏁

Semver: major.minor.patch eg. 1.4.5

| Flag | Description | Semver | | -------- | ------------------------------------------------------------------------------------------------------ | ------ | | feat | A new feature | Minor | | fix | A bug fix | patch | | docs | Documentation only changes | patch | | style | Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) | - | | refactor | A code change that neither fixes a bug nor adds a feature | patch | | perf | A code change that improves performance | patch | | test | Adding missing or correcting existing tests | patch | | chore | Changes to the build process or auxiliary tools and libraries such as documentation generation | patch |

No Major release

My current thinking is that major releases shouldn't be automated. If you think it should, create an issue.

What it doesn't do

  • Create artefacts
  • Push or pull branches
  • Updates your package.json
  • Use any other semantic versioning

Testing

npm test

Next steps

  • Generate a change log? (read)
  • Create an artefact? (read)

Alternative tools

Thank yous

  • Eric Elliot - Still not using his good functional programming principles but his lessons on modularity are awesome
  • Jest - Especially code coverage.
  • Typescript - It's not a Typescript project but the --checkJs option catches lots of code correctness issues when using docblock comments.
  • Husky - Preventing me from committing errors
  • ESLint - Keeps my code tidy
  • Prettier - Prevents me from having to worry about style issues.

Resources