The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Top 23 Formatter Open-Source Projects
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
biome
A toolchain for web projects, aimed to provide functionalities to maintain them. Biome offers formatter and linter, usable via CLI and LSP.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
globalize
A JavaScript library for internationalization and localization that leverages the official Unicode CLDR JSON data
-
prettier-eslint
Code :arrow_right: prettier :arrow_right: eslint --fix :arrow_right: Formatted Code :sparkles:
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Project mention: Shared Data-Layer Setup For Micro Frontend Application with Nx Workspace | dev.to | 2024-04-25Prettier: An opinionated code formatter that enforces a consistent code style.
Project mention: How to setup Black and pre-commit in python for auto text-formatting on commit | dev.to | 2024-03-29$ git commit -m "add pre-commit configuration" [INFO] Initializing environment for https://github.com/psf/black. [INFO] Installing environment for https://github.com/psf/black. [INFO] Once installed this environment will be reused. [INFO] This may take a few minutes... black................................................(no files to check)Skipped [main 6e21eab] add pre-commit configuration 1 file changed, 7 insertions(+)
YAPF (Yet Another Python Formatter): YAPF takes a different approach in that it’s based off of ‘clang-format’, a popular formatter for C++ code. YAPF reformats Python code so that it conforms to the style guide and looks good.
{ "$schema": "https://biomejs.dev/schemas/1.7.0/schema.json", "organizeImports": { "enabled": true }, "files": { "ignore": ["package.json", "package-lock.json"] }, "linter": { "enabled": true, "rules": { "recommended": true, "style": { "noUnusedTemplateLiteral": "off" } } }, "formatter": { "indentStyle": "space", "indentWidth": 4, "lineWidth": 320 }, "javascript": { "formatter": { "semicolons": "asNeeded" } } }
* The shell itself is https://github.com/mvdan/sh, a bash-like command interpreter
isort: This library sorts your imports alphabetically, and automatically separates them into sections and by type. It provides a cleaner and more organised way to manage project imports.
The author provides very surface-level criticism of two Rust tools, but they don't look into why those choices were made.
With about five minutes of my time, I found out:
wrap_comments was introduced in 2019 [0]. There are bugs in the implementation (it breaks Markdown tables), so the option hasn't been marked as stable. Progress on the issue has been spotty.
--no-merge-sources is not trivial to re-implement [1]. The author has already explained why the flag no longer works -- Cargo integrated the command, but not all of the flags. This commit [2] explains why this functionality was removed in the first place.
Rust is open source, so the author of this blog post could improve the state of the software they care about by championing these issues. The --no-merge-sources error message even encourages you to open an issue, presumably so that the authors of Cargo can gauge the importance of certain flags/features.
You could even do something much simpler, like adding a comment to the related issues mentioning that you ran into these rough edges and that it made your life a little worse, or with a workaround that you found.
Alternatively, you can continue to write about how much free software sucks.
[0]: https://github.com/rust-lang/rustfmt/issues/3347
[1]: https://github.com/rust-lang/cargo/pull/10344
[2]: https://github.com/rust-lang/cargo/commit/3842d8e6f20067f716...
AutoPEP8: This tool automatically formats Python code to conform to the PEP 8 style guide. It uses pycodestyle, a library that encapsulates the functionality of the original pep8 tool.
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.
Project mention: Oxlint – written in Rust – 50-100 Times Faster than ESLint | news.ycombinator.com | 2023-12-15
I've been using pint for formatting php files with null-ls.nvim. Few days ago null-ls.nvim has announced that the plugin will be archived in few months so I started migrating all my formatters and linter from null-ls to efm-langserver. I got other things such as prettier, black, isort, mypy, etc. working but can't get pint to work with php files: If I run pint via efm-langserver, everything is deleted from the buffer, and the saved file is formatted separately. How do I setup efm-langserver correctly to work with pint? Below is my config.yml for pint currently. yaml tools: pint: &pint format-command: "pint --no-interaction --quiet ${INPUT}" format-stdin: false languages: php: - <<: *pint Thank you.
Project mention: Pronto: Quick automated code review of your changes | news.ycombinator.com | 2024-03-06
Project mention: Am I the only one who doesn't put parentheses around the parameters in Ruby method definitions? | dev.to | 2024-04-11Rubocop has a default rule that says to put parentheses when there are parameters; even Standardrb has a default ([https://github.com/standardrb/standard/blob/8307fa8f449f896075ccad 74bf6a128ed2c26189/config/base.yml#L1098:title])
Project mention: Using PSScriptAnalyzer to check PowerShell version compatibility - Building custom compat profiles | /r/sysadmin | 2023-06-19I am looking to build a custom profile for a ws2019 with ps 7.2 + to use to check my scripts, i have tried using the compat collector https://github.com/PowerShell/PSScriptAnalyzer/tree/development/PSCompatibilityCollector and running the build.ps1 script there but I do not see an output for my commands and the script text doesn't provide much clarify to me at least.
Formatter related posts
- Setting up Doom Emacs for Astro Development
- Biome.js : Prettier+ESLint killer ?
- Most basic code formatting
- Am I the only one who doesn't put parentheses around the parameters in Ruby method definitions?
- Biome – fast JavaScript linter and formatter
- Rescuing legacy Node.js projects with Bun
- What is the most useful project you've ever worked on?
-
A note from our sponsor - WorkOS
workos.com | 26 Apr 2024
Index
What are some of the best open-source Formatter projects? This list will help you:
Project | Stars | |
---|---|---|
1 | prettier | 48,241 |
2 | black | 37,376 |
3 | yapf | 13,651 |
4 | biome | 10,237 |
5 | sh | 6,771 |
6 | isort | 6,314 |
7 | rustfmt | 5,761 |
8 | google-java-format | 5,413 |
9 | prettier-vscode | 5,032 |
10 | gts | 4,926 |
11 | globalize | 4,777 |
12 | autopep8 | 4,517 |
13 | spotless | 4,161 |
14 | prettier-eslint | 3,929 |
15 | dprint | 2,933 |
16 | uncrustify | 2,797 |
17 | pint | 2,673 |
18 | Pronto | 2,591 |
19 | standard | 2,589 |
20 | vim-autoformat | 2,220 |
21 | sql-formatter | 2,142 |
22 | neoformat | 1,943 |
23 | PSScriptAnalyzer | 1,775 |
Sponsored