@mayorovad I think you should use the prettier plugin for eslint and remove all formatting rules from eslint because afaik we Prettier is used in this project to format the code.

To be honest, I am not sure if prettier is enforced right now, but if it isn't, it probably should be. That would make the Eslint config a lot easier as well.

Thank you @Kurt29 ! Bumped prettier, added plugin for eslint integration and also added script to run it. Can you check ec59cb8 - is everything looks right?

Thank you @Kurt29 ! Bumped prettier, added plugin for eslint integration and also added script to run it. Can you check ec59cb8 - is everything looks right?

This commit LGTM

But should check that the version bump doesn't affect too much code. Cannot try that out right now for me

I'm sorry, this edits is beyond the scope of PR, but it is what it is 😸. Edited base tsconfig.json and changed target from es2020 to es6. Size of transpiled code almost the same (2.35 Mb vs 2.38 Mb), but it will provide better compatibility overall i think. What do you think @tbouffard @Kurt29 ?

To be honest, I am not sure if prettier is enforced right now, but if it isn't, it probably should be. That would make the Eslint config a lot easier as well.

@Kurt29 Prettier is not enforced but we would like because formatting issues are regularly introduced (for instance, see #88 (review) or #77)
So, if we can have prettier run along with eslint as you suggest, this will be great.

@mayorovad are we forced to change the TypeScript configuration as part of this PR? I can review the eslint configuration but I don't have time for now to check the impact of changing the transpile configuration (what you propose seems ok but I would like more time to discuss with other people of this change)

@tbouffard I checked, with current set of rules in eslint config there is no need for tsconfig changes. In future we can add some rules that requires parser. For now reverted changes in all tsconfig.json!