Remove prettier config

[jcbhmr]

Going based on this sentiment:

So I just chose, there's nothing you can't do with named exports, so why not only use named exports. It's all about reducing options and streamlining, unifying, calming the mind. ;)
#60 (comment)

Reducing the amount of customization seems like a good idea. Prettier themselves even recommend against modifying the config! 😊

By far the biggest reason for adopting Prettier is to stop all the ongoing debates over styles.
https://prettier.io/docs/en/option-philosophy.html

Sidenote: Prettier auto-includes any prettier-plugin-* packages, so you don't need the plugins: [] option at all

[jcbhmr]

IMO the default options are pretty universal. You never have to think about it again. No configuring, just npx prettier -w . and you're done. I really wish they respected the .gitignore so I didn't have to do --ignore-path .gitignore though to avoid formatting dist 😭

[jcbhmr]

In the future, @mesqueeb you might want to consider adopting a widespread eslint config preset like:

• https://github.com/xojs/xo#readme
• https://github.com/sindresorhus/eslint-plugin-unicorn#preset-configs
• https://www.npmjs.com/package/eslint-config-airbnb

Or make your own! 🥳

[jcbhmr]

Sidenote: prettier just released Prettier v3! https://prettier.io/blog/2023/07/05/3.0.0.html

[mesqueeb]

will close this one in favour of bb6c47e

Not ready yet to get rid of prettier config sorry 😅 life's too short to look at semicolons.

Looked into a couple of eslint tools / plugins, decided to go with eslint-plugin-unicorn
I bundled everything at @cycraft/eslint