format-css
prettier-eslint
format-css | prettier-eslint | |
---|---|---|
1 | 6 | |
9 | 3,935 | |
- | 0.6% | |
7.9 | 6.2 | |
4 days ago | 1 day ago | |
JavaScript | 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.
format-css
-
Building a lightweight CSS formatter
If you want to see more: the source code for this can be found on GitHub, where I'm currently in the process of making this a standalone NPM package.
prettier-eslint
-
help with create-react-app and eslint/prettier
Use the other one, prettier-eslint this is so that the code goes through Prettier before ESLint and not the other way around causing it to show issues that will be fixed once ESLint fixes it.
- Prettier and how to get most out of it
-
Why can't they tho?
Same, I can't stand some of prettier's opinions/style conversions and they refuse to add more options to their config file, so people literally have to make an entirely separate plugin just to deal with the issue of its config not being able to match your eslint config.
-
Setting up ESLint & Prettier in ViteJS
prettier-eslint
-
I always have a hard time configuring my projects
side note: you can use prettier-eslint (as opposed to the prettier eslint plugin) which runs prettier and then eslint --fix. that way you won't get annoyed by a shit ton red lines from eslint linting with prettier.
-
Boilerplate with React 17, Webpack 5, Tailwind 2, using babel, sass, with a hot dev server and an optimized production build
And I just ripped out my prettierrc/prettier recently, and still need some tweaking in this area, and might even add it it back. After looking at that plugin, it looks like it just DISABLES things in ESLint that Prettier handles, so you might have to add the prettier script and a .prettierrc config file. At least that is how I understand it. I was just looking at prettier's docs and saw this though - https://github.com/prettier/prettier-eslint, which seems like it might be what you are looking for.
What are some alternatives?
globalize - A JavaScript library for internationalization and localization that leverages the official Unicode CLDR JSON data [Moved to: https://github.com/globalizejs/globalize]
twin.examples - Packed with examples for different frameworks, this repo helps you get started with twin a whole lot faster.
csstree - A tool set for CSS including fast detailed parser, walker, generator and lexer based on W3C specs and browser implementations
prettier-eslint-cli - CLI for prettier-eslint
react-webpack-5-tailwind-2 - React 17 Boilerplate with Webpack 6, Tailwind 2, using babel, SASS/PostCSS, HMR, dotenv and an optimized production build
eslint-plugin-prettier - ESLint plugin for Prettier formatting
eslint-config-prettier - Turns off all rules that are unnecessary or might conflict with Prettier.
linters - CSSSR's linting configs for Prettier and ESLint.
prettier-plugin-apex - Code formatter for the Apex Programming Language
plugin-ruby - Prettier Ruby Plugin
vitte - A non SSR Starter Template using Svelte, Vite, Tailwind JIT. And Routify.
twind - The smallest, fastest, most feature complete Tailwind-in-JS solution in existence.