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

@betahuhn/config

v1.2.0

Published

Common configuration files for my projects

Downloads

270

Readme

🛠️ BetaHuhn config files

This repository contains common configuration files for my projects. It is based on Koj's config repo, I only changed the linter to eslint and modified some other things to my preference.

💻 Usage

Install the package as a dev dependency from npm:

npm install --save-dev @betahuhn/config

Eslint

This config includes the ESLint configuration I use in my personal projects. To use this configuration, create an ESLint config file .eslintrc.js in the project root:

module.exports = require("@betahuhn/config").eslint;

Semantic Release

I use Semantic Release for automated deployments of my packages. The configuration adds support for Gitmoji commits, creating release notes with a CHANGELOG.md, and publishing to GitHub and npm.

Create a Semantic Release config file release.config.js in the project root. If you want to release the master or production branches, you can use the import directly:

module.exports = require("@betahuhn/config").master;

Alternately, you can specify the branch you want to release:

module.exports = require("@betahuhn/config").release("branch-name");

Here are all the emojis which trigger a new release:

Major:

  • :boom: = Introduce breaking changes

Minor:

  • :sparkles: = Introduce new features

Patch:

  • :bug: = Bug fix
  • :ambulance: = Critical hotfix
  • :lock: = Fix security issues
  • :recycle: = Refactor code
  • :lipstick: = Add/update the UI and style files
  • :alien: = Update code due to external API changes
  • :package: = Add/Update compiled files or package

📄 License

MIT © Maximilian Schiller and Koj