Add prettier and eslint

[MichaelBuessemeyer]

This PR adds prettier as a formatter and eslint as a linter.

We use eslint as a linter and not prettier as eslint is more capable & has more features as far as I know.

Happy to hear / read your suggestions :)

[cmfcmf]

Hey @MichaelBuessemeyer,

thanks a lot for this PR! One thing that I would like to discuss is the addition of eslint. I think it is slightly overkill for this project and I am slightly in favor of not adding it (but you can definitely convince me otherwise).

Also, I would prefer if you added just two new scripts to package.json: format and lint, that run prettier (and possibly eslint), where format is a combination of the current pretty and lint-fix scripts and lint is a combination of am-i-pretty and lint.

[MichaelBuessemeyer]

thanks a lot for this PR!

Your welcome :)

One thing that I would like to discuss is the addition of eslint. I think it is slightly overkill for this project and I am slightly in favor of not adding it (but you can definitely convince me otherwise).

I understand that you think that eslint is overkill. But it has the advantage that it lints the code 😅 . This prevent some errors that might not be obvious at first sight. I only found the error in element.js (see above) thanks to eslint. Therefore using eslint can prevent these errors.

I am fine if you do not want it as a dependency. But i'll use it in #13 anyway to prevent myself from writing error that the linter can catch easily.

Also, I would prefer if you added just two new scripts to package.json: format and lint, that run prettier (and possibly eslint), where format is a combination of the current pretty and lint-fix scripts and lint is a combination of am-i-pretty and lint.

Alrighty 🐈

[cmfcmf]

Alright, thank you! I re-added eslint-config-prettier to avoid any potential conflicts between Prettier and ESLint, and added yarn lint to the GitHub action.