eslint-config-prettier
eslint-config-standard
Our great sponsors
eslint-config-prettier | eslint-config-standard | |
---|---|---|
17 | 7 | |
5,192 | 2,547 | |
1.7% | 0.4% | |
6.9 | 8.7 | |
17 days ago | 3 days ago | |
JavaScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
eslint-config-prettier
-
Adding code formatting, linting, pre-commit hooks and beyond...
As I was reading the Prettier documentation I stumbled upon this blob which talks about how to make ESLint and Prettier play nicely with each other. It instructed to install eslint-config-prettier dependency in my project using the command npm install --save-dev eslint-config-prettier. Then I added prettier as part of the .eslintrc.cjs' extends array making prettier dependency part of the linting process. Lastly, I ran its cmd line helper npx eslint-config-prettier path/to/main.js to check if there were any ESLint rules which are unnecessary or would conflict with Prettier. The test results came out fine with no unnecessary or conflicting rules. The use case on how it works and why to use it is mentioned here.
-
It Takes 6 Days to Change 1 Line of Code
I wouldn’t say they’re arguing something completely different. A large subset of linting rules are by nature purely formatting rules. You can enforce line length with either prettier or a linter and both can auto fix the issue.
Because of this things like [`eslint-config-prettier`](https://github.com/prettier/eslint-config-prettier) exist to ensure conflicting eslint formatting rules are disabled if they can be handled by prettier.
-
Looking to improve... Review my code??
Also add this eslint plugin, which makes eslint play nice with prettier: https://github.com/prettier/eslint-config-prettier
-
React Library Builder using Rollup.js and Storybook
Linting is an important step in maintaining code quality, The React Library Builder uses ESLint and eslint-config-prettier for linting. You can modify linting rules by overriding them in the .eslintrc file.
-
Setting up ESLint & Prettier in ViteJS
eslint-config-prettier: An ESLint configuration which disables the formatting rules in ESLint that Prettier is going to be responsible for handling, hence avoiding any clashes.
-
Modern, faster alternatives to ESLint
The eslint-config-prettier package disables all ESLint rules that might conflict with Prettier. This lets us use ESLint configurations without letting it get in the way when using Prettier. We can then use the eslint-plugin-prettier package to integrate Prettier rules into ESLint rules. Finally, we must set the Prettier rules in the ESLint configuration file. Add the following configuration to the .eslintrc file in the root directory of the application:
-
eslint-config-canonical: 1,000+ rules ESLint rules
eslint-config-prettier:
-
Understanding the Modern Web Stack: Prettier
To automatically disable all ESLint rules that conflict with prettier you can use eslint-config-prettier as follows:
-
Automatically lint & format your code on commit when using Next.js
Some of the ESLint rules Next.js comes pre-configured with are about formatting. But we want Prettier to handle everything related to the formatting of our code. This is why we'll install eslint-config-prettier and add it to our .eslintrc, where it will disable all existing rules that might interfere with Prettier.
-
Getting Started with Next.js - VSCode, ESLint and Prettier
Now since some prettier configs may conflict with ESLint, we need to turn off conflicting rules. This can easily be done by adding eslint-config-prettier:
eslint-config-standard
-
PURISTA - Thanks to amazing open-source software
eslint-config-standard
-
Setting up ESLINT with TS/JS in your React project in 2023
Based on your requirements and environment, answer the questions accordingly. At least with eslint version 8.0.1, you are only presented with 2 style guides: standard and XO. Personally, I prefer the standard styling guide but at any give time, it is a personal choice and as such feel free to choose any from a bunch of available options. Once all dependencies are installed, ensure that you have the following packages added as devDependencies to your project:
-
[AskJS] favorite JavaScript library
Hmm right, haven't found too many controversial things in https://github.com/standard/eslint-config-standard/blob/master/.eslintrc.json, besides no-semi fixed by semi-standard and comma-dangle "never" (sucks for git history, they should allow it for multiline cases https://eslint.org/docs/rules/comma-dangle#always-multiline)
-
Some tips on tooling for improving our code
ESLint plugin for StandardJS; allows you to format code as StandardJS, but clear more serious errors too.
-
A notable JavaScript developer shamelessly copied one of my most downloaded nod
The JS Open Source Community is filled with people grifting things like this. Quite notably, there's a linter called JS Standard Style, which actually has nothing to do with JS Standards.
It's marketed as if it was a standard, the fact that it isn't is tucked away in the readme, and also -- the entire project is just a wrapper around someones .eslintrc file, yet barely any credit is given to the ESLint devs who do all the work.
Go ahead and read the readme here, https://github.com/standard/standard. Could you genuinely tell this wasn't really a JS Standard at a glance? Could you tell this was just a config file for someone elses work? None of the donations go upstream to eslint by the way.
Hell, the actual config file is hidden inside a sub repo:
https://github.com/standard/eslint-config-standard
which has the audacity to claim
> This module is for advanced users. You probably want to use standard instead :)
It's a config file for someone elses program! Why does this library go through so much effort to hide that it's just someones config file? Why on earth is it called JS Standard Style?
The whole community is filled with slimy nonsense like this.
-
JavaScript Is Weird
Eslint is the default linter. Standard is a curated list of rules with good quality.
https://github.com/standard/eslint-config-standard
I would start with that and tweak what you don't like
-
Getting Started with Next.js - VSCode, ESLint and Prettier
Well done, we managed to set up ESLint using Airbnb’s JavaScript styling guide to our newly created Next.js project. You could have used another popular styling guide like Google, Standard, or even create your own to your liking.
What are some alternatives?
eslint-config-google - ESLint shareable config for the Google JavaScript style guide
prettier - Prettier is an opinionated code formatter.
eslint-plugin-prettier - ESLint plugin for Prettier formatting
react-webpack-5-tailwind-2 - React 17 Boilerplate with Webpack 6, Tailwind 2, using babel, SASS/PostCSS, HMR, dotenv and an optimized production build
webpack-react-typescript-starter - React App with Typescript, using webpack5 and styled-components
standard - Ruby's bikeshed-proof linter and formatter 🚲
prettier-eslint-cli - CLI for prettier-eslint
vitte - A non SSR Starter Template using Svelte, Vite, Tailwind JIT. And Routify.
twin.examples - Packed with examples for different frameworks, this repo helps you get started with twin a whole lot faster.
prettier-eslint - Code :arrow_right: prettier :arrow_right: eslint --fix :arrow_right: Formatted Code :sparkles:
linters - CSSSR's linting configs for Prettier and ESLint.