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-carnesen

v13.0.0

Published

ESLint configurations for @carnesen projects

Downloads

47

Readme

ESLint configurations for @carnesen projects. This package is thoroughly documented, tested, and maintained. Feel free to use it in your own projects.

build status badge npm version badge github stars badge

Usage

To install this package as a dependency in your project, do:

npm install eslint-config-carnesen eslint

Now create a file .eslintrc.json at the root of your project with contents:

{
  "extends": [
    "eslint-config-carnesen"
  ]
}

The main export eslint-config-carnesen has rules for Node.js and React. If your codebase is Node.js only, instead do:

{
  "extends": [
    "eslint-config-carnesen/node.eslintrc.json"
  ]
}

Or for React-only code:

{
  "extends": [
    "eslint-config-carnesen/react.eslintrc.json"
  ]
}

In any case, add these lines to your package.json's "scripts" field:

    "lint": "eslint --ext .js,.jsx,.ts,.tsx <source code directory>",
    "lint:fix": "npm run lint -- --fix",

where <source code directory> is the subdirectory of your project containing the source code that you want to lint. Finally add && npm run lint to your package's "test" script to make sure you don't forget to lint! I strongly recommend setting up your editor to automatically fix lint errors on save. That way the linter mostly stays out of your way and just does the right thing. In Visual Studio Code, this plugin works great.

Rules

This package's rules extends those espoused by by AirBnB, consumed as eslint-config-airbnb. Those rules are mostly concerned with syntax. For code formatting, this package uses eslint-config-prettier, which disables all rules that are unnecessary or might conflict with Prettier. Instead of calling prettier directly, this package employs eslint-plugin-prettier, which "runs Prettier as a ESLint rule and reports differences as individual ESLint issues". I wrote up some thoughts here on why that's a much better approach than using eslint and prettier separately.

More information

If you encounter any bugs or have any questions or feature requests, please don't hesitate to file an issue or submit a pull request on this project's repository on GitHub.

Related

License

MIT © Chris Arnesen