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

skip-ci

v1.0.6

Published

✨ Automatically detect [skip ci] messages (and the like) in your last commit 🎉

Downloads

2,685

Readme

✨ Automatically detect [skip ci] messages (and the like) in your last commit 🎉

🏠 Homepage

When you include either a [skip ci] or a [ci skip] in your commit message, (most) CI systems understand it to mean, well, CI. This is generally useful when you're updating non-code portions of the repo, such as documentation or when you're fixing something irrelevant to the codebase.

However, if you're like me, you might use git hooks (perhaps using husky) to prevent bad code from being pushed in the first place by making tests run during pre-push hook. This generally works great, but it still runs the tests even when you add a [skip ci] to your commit message.

That's where this tool comes in. Just call skip-ci and you'll be able to detect & skip whatever commands you'd like when you don't want to run any tests. To see an example, just look at this repo's .huskyrc.yml!

Install

npm i skip-ci -D

This package has ZERO dependencies!

Usage

skip-ci && "Skipping CI..." || echo "Running tests..."

Development

Because we rely on a subrepo for testing the skip-ci tool, when cloning, make sure you add the --recursive flag.

Then, you can test skip-ci (or more specifically, cli.js) by running npm test, which will go through each commit of the test repo (repo/) and check that the tool recognizes [skip ci] and [ci skip] and returns the appropriate exit codes.

And don't forget to npm i when developing to install devDependencies (mainly linting).

Author

👤 Jane Jeon [email protected]

  • Website: https://janejeon.dev
  • Github: @JaneJeon

🤝 Contributing

Contributions, issues and feature requests are welcome!Feel free to check issues page.

Show your support

Give a ⭐️ if this project helped you!

📝 License

Copyright © 2022 Jane Jeon [email protected]. This project is LGPL licensed.

TL;DR: you are free to import and use this library "as-is" in your code, without needing to make your code source-available or to license it under the same license as this library; however, if you do change this library and you distribute it (directly or as part of your code consuming this library), please do contribute back any improvements for this library and this library alone.