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

@helloalfred/eslint-config

v1.2.1

Published

Shared ESLint configurations

Downloads

95

Readme

@helloalfred/eslint-config

An ESLint shareable config for TypeScript app in HelloAlfred world split into backend, frontend and mobile presets

Usage

Install the shared configs and its peer dependencies (This is due to a known limitation in ESLint.)

# Install the shared config
yarn add --dev @helloalfred/eslint-config

# Install common peer dependencies
# If you use zsh, then wrap all of them in ""
yarn add --dev @typescript-eslint/eslint-plugin@^4.15.0 @typescript-eslint/parser@^4.14.2 eslint@^7.19.0 eslint-config-prettier@^7.2.0 eslint-plugin-import@^2.22.1 eslint-plugin-prettier@^3.3.1 prettier@^2.2.1

# Install the peer dependencies (frontend/mobile only)
yarn add --dev eslint-plugin-jest@^24.1.3 eslint-plugin-jsx-a11y@^6.4.1 eslint-plugin-react@^7.22.0 eslint-plugin-react-hooks@^4.2.0

# Install peer dependencies (mobile only)
yarn add --dev [email protected]

# Install the peer dependencies (backend only)
yarn add --dev @typescript-eslint/eslint-plugin@^4.15.0 @typescript-eslint/eslint-plugin-tslint@^4.15.0 tslint@^6.1.3

The shared config includes linting rules for:

  • Mobile
  • Frontend
  • Backend

Now its time to create your .eslintrc.js file, for that you will need to create the file and extend @helloalfred/eslint-config/<backend|frontend|mobile>, below is an example for a frontend app. Since we are dealing with typescript projects, me need to specify parserOptions and point it to the projects tsconfig.json

// .eslintrc.js
module.exports = {
  extends: ['@helloalfred/eslint-config/frontend'],
  parserOptions: {
    project: ['./tsconfig.json'],
    sourceType: 'module',
    tsconfigRootDir: __dirname,
  },
};

Note: Please read some important instructions regarding the project option here.

There are some more parserOptions you may care about.