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

@12core/eslint-config-12core

v5.0.0

Published

12Core Shareable eslint config

Downloads

71

Readme

eslint-config-12core

Node.js CI

A shareable eslint config for 12core projects.

Usage

npm i @12core/eslint-config-12core eslint --save-dev

Then create an .eslintrc.json file in the root of your directory:

{
  "extends": "@12core/eslint-config-12core"
}

Then run eslint on whatever code you want to lint:

eslint --ext .js esm/

Make the linting step part of your testing script.

What

@12core/eslint-config-12core bundles standard + standard-jsx with additional consutomizations that work for all of us at little-core-labs.

Because we control the shareable config, the normally peer-dependent eslint plugins are actually included as transient dependencies, so that usage of this config is a lot more convenient (only 2 deps, instead if 5+).

Contributing

If you would like to make rule changes, please submit a PR with some discussion with rational.

Editor plugins

You should use an editor plugin so that you can see the warnings while working, and take advantage of auto formatting:

VSCode

Sublime

Your favorite editor

... please PR notes you have!

React

If you want to use the standard react plugin, follow these steps:

Install deps

npm i @12core/eslint-config-12core eslint babel-eslint eslint-config-standard-react --save-dev

Create eslint config

Create a .eslintrc.json with the following.

{
  "parser": "babel-eslint",
  "extends": ["@12core/eslint-config-12core", "standard-react"]
}

Run eslint

eslint --ext .js esm/