https://github.com/frencojobs/minimalistic
Opinionated but sensible and minimal prettier config with plugins
https://github.com/frencojobs/minimalistic
prettier prettier-config
Last synced: 8 months ago
JSON representation
Opinionated but sensible and minimal prettier config with plugins
- Host: GitHub
- URL: https://github.com/frencojobs/minimalistic
- Owner: frencojobs
- License: mit
- Created: 2021-08-07T14:54:14.000Z (almost 5 years ago)
- Default Branch: main
- Last Pushed: 2022-07-31T19:38:10.000Z (almost 4 years ago)
- Last Synced: 2025-09-20T04:02:02.904Z (9 months ago)
- Topics: prettier, prettier-config
- Language: JavaScript
- Homepage: https://npm.im/minimalistic
- Size: 51.8 KB
- Stars: 5
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README

Opinionated but sensible and minimal prettier config with plugins.
> **Disclaimer**
>
> The title `minimalistic` doesn't reflect the config but rather stands for the style of the formatted code which is minimal and clean with less syntactic tokens. In fact, the config is instead quite pedantic and strict.
## Usage
Install the package as a `devDependency` by your package manager of choice.
```sh
npm i -D minimalistic
```
Set `prettier` config in `package.json` as `minimalistic`.
```json
{
"prettier": "minimalistic"
}
```
> Make sure you have both `prettier` and `typescript` installed as `devDependencies`. `typescript` is used by an included plugin to organize imports. It doesn't mean you have to use TypeScript. The plugin works with JavaScript as well.
## Rationale
1. To reduce as much space as possible where it makes sense to. This is done via disallowing whitespaces between braces, disabling semicolons and using single quotes instead of double quotes, etc.
2. Trailing commas are preferred for better git diffs.
3. To have import statements always organized. This may be opinionated but it helps with OSS projects where different parties may have different opinions on how imports should be organized or maybe different IDE setups. Some people really don't care about this but they hate it when submitted PRs have unnecessary import-sorting changes. This will also help them.
4. To have `package.json` organized with reasons same as above.