pretty-quick
eslint-config-prettier
pretty-quick | eslint-config-prettier | |
---|---|---|
6 | 17 | |
2,173 | 5,233 | |
0.4% | 0.8% | |
6.8 | 6.6 | |
27 days ago | 19 days ago | |
TypeScript | JavaScript | |
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.
pretty-quick
-
npx looking first in the global cache and not local project node_modules
recently my team started facing this issue about pretty-quick not compatible with [[email protected]](mailto:[email protected]). (https://github.com/azz/pretty-quick/issues/164)
-
Setting up ESLint & Prettier in ViteJS
If you'd like, you can go a bit further and automate the linting and formatting process a bit. I like to use Husky which allows you to run your linter, tests etc. on a git commit/push etc. You can also then use pretty-quick along with husky to automatically format your code whenever you git commit, just in case someone on your team hasn't set it up in their IDE.
-
How to properly set up Prettier in less than 2 minutes
By using husky and pretty-quick, you can automatically force every developer to format all the changed files (and nothing more) every time they commit.
-
Adding Prettier to a Project
Set up commit hooks with pretty-quick and husky. First, install them as dev dependencies:
-
Awesome Dev Tools To Automate Code Tasks 🔥
In this tutorial, we will also use commitlint and pretty-quick libs to check if your commit messages meet the conventional commit format and run prettier on changed files respectively.
-
How to set Husky
So basically husky is "Git hooks made easy" and we are going to use to automatically format all of our code that is staged for our commits, so we are going to use the "pre-commit" hook to run pretty-quick a simpler way to run our prettier scripts with configuration
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.
-
[AskJS] Does anyone enjoy using Eslint?
If you use Prettier you should disable any and all eslint formatting rules. It's just not worth the hassle trying to make them "compatible". Fortunately there's an easy way to do that with a plugin.
- ESLint and Prettier conflict
-
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
-
Any way to disable prettier diagnostics in eslint-lsp
If you don’t care about the diagnostics, you should be using this instead. Prettier even says so.
-
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.
-
Do you use eslint and/or prettier?
You can use both Eslint and Prettier if you care greatly about both linting and code formatting. Prettier had a plugin to disable Eslint's formatting rules.
-
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:
What are some alternatives?
prettier - Prettier is an opinionated code formatter.
eslint-config-google - ESLint shareable config for the Google JavaScript style guide
husky - Git hooks made easy 🐶 woof!
eslint-plugin-prettier - ESLint plugin for Prettier formatting
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
react-webpack-5-tailwind-2 - React 17 Boilerplate with Webpack 6, Tailwind 2, using babel, SASS/PostCSS, HMR, dotenv and an optimized production build
commitlint - 📓 Lint commit messages
webpack-react-typescript-starter - React App with Typescript, using webpack5 and styled-components
prettier-eslint-cli - CLI for prettier-eslint
prettier-java - Prettier Java Plugin
vitte - A non SSR Starter Template using Svelte, Vite, Tailwind JIT. And Routify.