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-andyet-frontend

v0.0.0

Published

eslint configuration used in andyet react projects

Downloads

8

Readme

eslint-config-andyet-frontend

This is the base set of eslint rules for andyet frontend projects. It is built for linting different types of frontend code. If it doesn't work for the type of code you're writing, feel free to add it!

Currently it can lint for:

  • babel
  • react
  • require/import/export
  • webpack specific require/import/export

Installation and Usage

Currently eslint doesn't provide a great way to package plugins with configs, so any plugin used by the config you choose will have to be installed. To make that a little easier, each plugin needed is listed below for easy npm installing.

The required plugins are also not listed as peerDependencies because otherwise all plugins would need to be installed even if they weren't being used.

Base

The base config just includes the common rules for frontend browser development, along with the import plugin which handles some common cases of making sure the stuff you require is actually there.

npm install eslint eslint-config-andyet-frontend eslint-plugin-import --save-dev
{
  "extends": ["andyet-frontend"]
}

Babel

The babel config adds on top of the base config above, but makes sure the linter parses your code using the plugins and presets you've configured for babel.

npm install eslint eslint-config-andyet-frontend eslint-plugin-import babel-eslint --save-dev
{
  "extends": ["andyet-frontend/babel"]
}

React

The react-webpack config adds on top of the react config above, but adds rules for react and also assumes you're using babel.

npm install eslint eslint-config-andyet-frontend eslint-plugin-import eslint-plugin-react babel-eslint --save-dev
{
  "extends": ["andyet-frontend/react"]
}

React & Webpack

The react config adds on top of the base config above, but also configures the import plugin so it will follow paths setup by your webpack.config.

npm install eslint eslint-config-andyet-frontend eslint-plugin-import eslint-plugin-react babel-eslint eslint-import-resolver-webpack --save-dev
{
  "extends": ["andyet-frontend/react-webpack"]
}

Webpack

The webpack config adds on top of the base config above, but adds rules for react and also assumes you're using babel.

npm install eslint eslint-config-andyet-frontend eslint-plugin-import eslint-import-resolver-webpack --save-dev
{
  "extends": ["andyet-frontend/webpack"]
}

Contributing

If you want to add some rules to this, they should go in a new file inside the configs/ directory.

Then you can combine any of those configs into a top level config file. Check out react-webpack.js for an example.

You could also add a test file inside tests/, if you want to test that some specific syntax is linted properly.