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

@fewlines/eslint-config

v3.1.2

Published

Downloads

19

Readme

= eslint-config :toc: preamble

Disclaimer: this package is made for our internal usage and is only open source for convenience so we might not consider Pull Requests or Issues. Feel free to fork though.

This package includes the different styles we apply to our JavaScript and TypeScript code.

⚠️ As this plugin wants to use a minimalist configuration, it relies on using prettier via ESLint which means you could have to configure your editor. The goal is to not have the editor run prettier directly as it would conflict with ESLint.

== Text Editor

=== VSCode

In order to integrate ESLint into VS Code, install these two extensions:

  • https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint[ESLint]
  • https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode[Prettier]

Then add these settings to your VSCode's settings.json:

[source, json]

"eslint.format.enable": true, "editor.defaultFormatter": "dbaeumer.vscode-eslint", "[javascript]": { "editor.defaultFormatter": "dbaeumer.vscode-eslint" }, "[javascriptreact]": { "editor.defaultFormatter": "dbaeumer.vscode-eslint" }, "[typescript]": { "editor.defaultFormatter": "dbaeumer.vscode-eslint" }, "[typescriptreact]": { "editor.defaultFormatter": "dbaeumer.vscode-eslint" }, "[graphql]": { "editor.defaultFormatter": "dbaeumer.vscode-eslint" }, "[json]": { "editor.defaultFormatter": "dbaeumer.vscode-eslint" }

If the linter does not work right away, you can pop the VS Code command palette with ⌘ Cmd + ↑ Shift + P on mac, or Ctrl + ↑ Shift + P on windows/linux, and set the default formatter:

image::https://user-images.githubusercontent.com/31956107/75045130-06f07800-54c3-11ea-8881-f9c9a50efea9.gif[VS Code default linter gif]

For more information, https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint[check this part of the ESLint documentation].

=== Vim

Vim users could use https://github.com/dense-analysis/ale[ALE] and use let g:ale_fix_on_save = 1 and eslint as the linter for JavaScript and TypeScript.

== General rules

To enforce consistency throughout our imports and exports, we are using https://www.npmjs.com/package/eslint-plugin-import[eslint-plugin-import].

=== Import

The set of rules we chose to organize our imports are the following groups:

  • Built in and externals
  • Parents, siblings, indexes and path aliases

[source, js]

import { IncomingMessage, ServerResponse } from "http"; import React from "react"

import { CustomError } from "@src/errors" import { Handler } from "./handler";

=== Export

For export rules, we are using:

  • https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/group-exports.md[group-exports].
  • https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/exports-last.md[exports-last].

== Usage

This plugin offer several configurations depending on your project type.

=== Node project

[source, shell]

yarn add -D @fewlines/eslint-config eslint
eslint-config-prettier eslint-plugin-prettier prettier
eslint-plugin-import

Then add these lines to your package.json:

[source, json]

"eslintConfig": { "extends": "@fewlines/eslint-config/node" }

=== TypeScript project

[source, shell]

yarn add -D @fewlines/eslint-config eslint
eslint-config-prettier eslint-plugin-prettier prettier
@typescript-eslint/eslint-plugin @typescript-eslint/parser
eslint-plugin-import

Then add these lines to your package.json:

[source, json]

"eslintConfig": { "extends": "@fewlines/eslint-config/typescript" }

The TypeScript plugin extends the previous Node plugin so it is not needed.

=== React project

[source, shell]

yarn add -D @fewlines/eslint-config eslint
eslint-config-prettier eslint-plugin-prettier prettier
eslint-plugin-react
eslint-plugin-import

Then add these lines to your package.json:

[source, json]

"eslintConfig": { "extends": "@fewlines/eslint-config/react" }

The React plugin extends the previous Node plugin so it is not needed.

=== React + TypeScript project

⚠️ This preset only aim to remove the prop-types checks. You should use it along the react and typescript presets.

[source, shell]

yarn add -D @fewlines/eslint-config eslint
eslint-config-prettier eslint-plugin-prettier prettier
@typescript-eslint/eslint-plugin @typescript-eslint/parser
eslint-plugin-react
eslint-plugin-import

Then add these lines to your package.json:

[source, json]

"eslintConfig": { "extends": [ "@fewlines/eslint-config/typescript", "@fewlines/eslint-config/react", "@fewlines/eslint-config/react-typescript" ] }

The React + Typescript plugin extends the previous Node plugin so it is not needed.

=== Preact + TypeScript project

[source, shell]

yarn add -D @fewlines/eslint-config eslint
eslint-config-prettier eslint-plugin-prettier prettier
@typescript-eslint/eslint-plugin @typescript-eslint/parser
eslint-plugin-import

Then add these lines to your package.json:

[source, json]

"eslintConfig": { "extends": "@fewlines/eslint-config/preact-typescript" }

The Preact + Typescript plugin extends the previous Node plugin so it is not needed.

== Contributing

See xref:CONTRIBUTING.md[CONTRIBUTING.md].