eslint-plugin-prettier
tools
eslint-plugin-prettier | tools | |
---|---|---|
13 | 45 | |
3,178 | 24,334 | |
1.1% | - | |
7.6 | 0.0 | |
2 days ago | 8 months ago | |
JavaScript | Rust | |
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-plugin-prettier
-
Create React UI Lib 1.1: Ladle and ESLint
You can also add ESLint now (props to @femincan for the suggestion). It comes with recommended settings for these plugins: typescript, prettier, react, react-hooks, jsx-a11y.
-
How do I get eslint to work with prettier, TypeScript and null-ls?
I recommend installing and configuring the eslint-plugin-prettier package in your project: https://github.com/prettier/eslint-plugin-prettier
-
Setting up ESLint & Prettier in ViteJS
eslint-plugin-prettier
-
Why use prettier if ESLint can format?
Another approach that you can also take is a sort of "prettier as an ESLint plugin" option, such with eslint-plugin-prettier. The idea is that the developer only needs to run one tool (ESLint), but you add a plugin to ESLint that just calls prettier and converts the prettier error messages to ESLint error messages. I've worked at companies that have used this approach, and it makes setting up your editor/IDE very simple, because you've only got one tool to configure. That said, I personally don't like it because it forces you to use ESLint's "auto fix" functionality, which I find works well for formatting, but IME less well for some of the other lints.
-
Introducing Swarmion ๐, a Type-safe Serverless Microservices Framework
A comprehensive set of formatting (through eslint-plugin-prettier) and linting rules, generated with Clinter. Once again, each package can easily extend the root configuration.
-
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:
-
Running prettier 40x faster than prettier CLI using dprint
We run prettier through eslint, and run eslint through jest which provides parallelism. eslint also has a cache... So I'm not sure what dprint gets you over that?
https://github.com/jest-community/jest-runner-eslint
https://github.com/prettier/eslint-plugin-prettier
-
[AskJS] Why is is prettier used if eslint can format?
I personally use eslint-plugin-prettier so Prettier formatting issues are shown in my editor and are reported when linting using ESLint.
-
The Ultimate Guide to TypeScript Monorepos
When installing the Prettier and ESLint extensions for VSCode, formatting and linting will also work within VSCode for any files in the monorepo. Only tweak required to make this work is to configure the Prettier plugin for ESLint (see example .eslintrc.json). Otherwise Prettier and ESLint will get in each otherโs way and make for a poor editing experience. To make this work, the following two settings will also need to be configured in a .vscode/settings.json configuration (see settings.json):
-
Starter using Vite + React + TypeScript + Tailwind CSS.
NOTICE: The template does not use eslint-plugin-prettier and prettier-eslint. So I recommend that running commands individually. e.g. prettier && eslint.
tools
-
Biome.js : Prettier+ESLint killer ?
Biome is a fork of Rome, which was originally an ambitious tool written in Rust but abandoned in October 2023. It includes both a linter and a formatter, putting an end to the time-consuming difficulties associated with reconciling ESLint and Prettier rules.
-
Rescuing legacy Node.js projects with Bun
When I saw the release of bun six months ago, I was not that hyped as I saw a tool that had similar ambitions, Rome, and dissapointed many. But it was different this time. It really is a drop in replacement for Node.js so you can start using it by replacing the npm and node commands in your package.json file. The main feature that captured my interest was the ability to use require and import statemtents in the same file. This allows you to keep using CommonJS modules and use import statemtents for any new modules that drop support for it. The only catch I could find so far is that if you decide to mix import and require statements, you cannot use module.exports but instead use export statement. I did exactly that and now I have a fully functional backend with admin panel that won't make your head scratch fighting with CommonJS and ESModules.
-
Build a Vite 5 backend integration with Flask
Once you build a simple Vite backend integration, try not to complicate Vite's configuration unless you absolutely must. Vite has become one of the most popular bundlers in the frontend space, but it wasn't the first and it certainly won't be the last. In my 7 years of building for the web, I've used Grunt, Gulp, Webpack, esbuild, and Parcel. Snowpack and Rome came-and-went before I ever had a chance to try them. Bun is vying for the spot of The New Hotness in bundling, Rome has been forked into Biome, and Vercel is building a Rust-based Webpack alternative.
-
BiomeJS 2024 Roadmap
It definitely existed by the time rome_console/biome_console was created! The crate was created 2 years ago[1] and miette was released more than 2 years ago[2]. By the time rome_console was created miette was on v4, so presumably somewhat mature.
[1]: https://github.com/rome/tools/commits/main/crates/rome_conso...
[2]: https://crates.io/crates/miette/versions
-
Biome
Biome formats and lints your JavaScript and TypeScript code in a fraction of a second. Biome is the community successor of Rome Tools [0].
As part of this announcement, we have released the first stable version of Biome [1]. Join us on our Discord [2] and support us via our open collective [3].
I am one of the main maintainers of Biome. I will be happy to answer any questions :)
[0] https://github.com/rome/tools
-
JavaScript Gom Jabbar
I have no idea how true this is, but the source of the claim seems to come from here:
https://github.com/rome/tools/discussions/4302
"But in short, the company Rome Tools ran out of funding, so the core team of last year are no longer working on the project."
-
Rome v12.1: a Rust-based linter formatter for TypeScript, JSX and JSON
For now, Rome implements most of the ESLint recommended rules (including TypeScript ESLint) and some additional rules that are enabled by default. In the future, you can expect a recommended preset that is a superset of the ESLint recommended preset. So if you're not heavily customising ESLint, you should be able to use Rome.
Otherwise, most of the rules are not fine-tunable in the way that ESLint is. Rome tries to provide the experience that Prettier provided in the formatting tool: good defaults for a near-zero configuration experience. It tries to adopt the conventions of the JS/TS community. Still, some configuration is provided when the community is divided on some opinions (e.g. space vs. tab indentation, semicolons or as-needed semicolons, ...).
There is an open issue [1] for listing equivalent rules between ESLint and Rome. Expect more documentation in the future, and maybe a migration tool.
If I had been one of the founders of Rome, I could have pushed for more compatibility with ESLint. In particular, using the same naming conventions and thus the same names for most rules, and recognising ESLint ignore comments.
[1] https://github.com/rome/tools/issues/3892
-
Rome
Today we are going to talk about Rome. According to their github page
-
Complete rewrite of ESLint (GitHub discussion by the creator)
I must say, although it doesn't (of course) have anywhere near the configuration or plugin-capability of eslint, I've found Rome impressive so far. I have access to a range of PCs and the performance boost of a compiled binary makes a pretty big difference on a large repo on a slower machine.
-
Porting 58000 lines of D and C++ to jai, Part 0: Why and How
Fast compilation seems very appealing. It is one of the main reason why I am interested into Go and Zig.
I recently started working with Rust for contributing to projects like Rome/tools [1] and deno_lint [2]. The compilation and IDE experience is frustrating. Compilation is slow. I am afraid that this is rooted to the inherent complexity of Rust.
[1] https://github.com/rome/tools
[2] https://github.com/denoland/deno_lint
What are some alternatives?
Tailwind CSS - A utility-first CSS framework for rapid UI development.
biome - A toolchain for web projects, aimed to provide functionalities to maintain them. Biome offers formatter and linter, usable via CLI and LSP.
vite - Next generation frontend tooling. It's fast!
yarn.build - Build ๐ and Bundle ๐ฆ your local workspaces. Like Bazel, Buck, Pants and Please but for Yarn Berry. Build any language, mix javascript, typescript, golang and more in one polyglot repo. Ship your bundles to AWS Lambda, Docker, or any nodejs runtime.
eslint-config-prettier - Turns off all rules that are unnecessary or might conflict with Prettier.
msgpack-tools - Command-line tools for converting between MessagePack and JSON / msgpack.org[UNIX Shell]
eslint-plugin-react - React-specific linting rules for ESLint
sucrase - Super-fast alternative to Babel for when you can target modern JS runtimes
vite-react-ts-tailwind-firebase-starter - Starter using Vite + React + TypeScript + Tailwind CSS. And already set up Firebase(v9), Prettier and ESLint.
deno_lint - Blazing fast linter for JavaScript and TypeScript written in Rust
dprint-vscode - Visual Studio Code extension for formatting code with dprint.
gcc