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

stacklint

v0.5.1

Published

Code-style and linting presets cli-tool to quickly scaffold project development

Downloads

18

Readme

Stacklint

Code-style and linting presets cli-tool to quickly scaffold project development.

npm npm npm

All stacks use lintstaged to run all linted stacks when code is commited to the git repository. We feel that this is a really nice approach to avoid un-linted code creeping into the codebase.

Because standard lint configuration files are used any related Code-editor plugins should pickup and follow the same ruleset, or when running individual linters directly.

When running stacklint all node and composer packages required to lint the selected stacks are added to your configuration files and individual config files for each stack are also included.

Installation

Stacklint is intended to be installed globally so that it can easily be run and there is no need to include the dependency in your project specific package.json.

npm install -g stacklint

Usage

stacklint [options] <stacks>

After installing your lint stacks you will need to run required installs.

npm install
composer install

Note: Because lintstaged installs some git hooks, you should initialise your git repository before running npm install after setting up your stacks.

Examples

The following example will setup all required files and packages to lint php and md Markdown files when they are committed to git.

stacklint php md json

Installs packages and configs for:

  1. Lintstaged
  2. PHP Codesniffer
  3. Markdownlint
  4. Jsonlint
stacklint js airbnb vue

Installs packages and config for:

  1. Lintstaged
  2. ESLint
    1. Airbnb extend
    2. Vue.js plugin
    3. Babel plugin

Available stacks

You can quickly check which stacks are available by running stacklint -l or stacklint --list.

  1. js (Javascript. Also required additional stack for style guide. E.g. airbnb)
    1. airbnb (Airbnb style guide)
  2. json
  3. laravel (Use instead of php if using laravel)
  4. md (Markdown)
  5. php (PSR-2)
  6. scss
  7. vue (Requires js stack)

Contributing

We welcome any contributions, especially new lint stacks.

Support

If you have any question or problems please open an issue (or submit a PR). Alternatively you can contact me, m2de on Twitter.