Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Adopt a more strict ESLint config

See original GitHub issue

Like airbnb 's javascript specification, which makes code easier to maintain

Issue Analytics

State:
Created 7 years ago
Comments:6 (4 by maintainers)

Top GitHub Comments

2reactions

SaraVieiracommented, Aug 20, 2017

@developit can I pick this up and try to place the preact one and prettier?

0reactions

marvinhagemeistercommented, Mar 18, 2019

In my opinion it’s safe to close this issue. There doesn’t seem to be any interest in changing our ESLint config in the past months. The Prettier initiative is awesome and can happen independently from this issue 👍

Top Results From Across the Web

Consider adopting '@rushstack/eslint-config' as a starting ...

Mild suggestion: The Microsoft team that produces rush, api-extractor, and other build tools maintains a "very very strict" reusable ESLint ...

strict - ESLint - Pluggable JavaScript Linter

A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.

Basic Features: ESLint - Next.js

Strict : Includes Next.js' base ESLint configuration along with a stricter Core Web Vitals rule-set. This is the recommended configuration for developers ...

eslint-config-pretty-strict - npm

This config provides reasonable ESLint rules to prevent errors, enforce best practices and keep a consistent style.

Upgrading to a stricter ESLint config - Thibaud's blog

Updating a codebase from one ESLint config to another can be daunting, especially if switching to something more strict.