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

eslint-config-ta

v6.0.0

Published

Reusable eslint config for TA web apps.

Downloads

56

Readme

eslint-config-ta

Circle CI

ESlint config for TechnologyAdvice.

npm i eslint-config-ta -D

Usage

Extend relevant ta/* rules in your .eslintrc.

Root Config

In the project root:

{
  "extends": [
    "ta",
    "ta/(backend|frontend)"
  ]
}

Test Config

Use the test config to customize rules for the /test directory:

{
  "extends": [
    "ta/(backend|frontend)/test"
  ]
}

Environment Detection

At the root of each group (e.g. ta, ta/(frontend|backend)) is an index.js file. It will select the appropriate configuration file based on the current NODE_ENV. For example, where your .eslintrc is:

{
  "extends": [
    "ta",
    "ta/frontend"
  ]
}

When you run NODE_ENV=production eslint . ./, eslint-config-ta will handle extending the correct configuration files, so under the hood it looks like this:

{
  "extends": [
    "ta/organization/production",
    "ta/frontend/production"
  ]
}

Releasing

On the latest clean master:

npm run release:major
npm run release:minor
npm run release:patch