Hi @tschaub I am interested on what tool did you use to clean up the files? prettier?

npm run lint -- --fix (which is like npx eslint benchmarks lib test tasks --fix) did most of the work. The ESLint config uses rules from Prettier, so part of the fix (and rule enforcement) is done by Prettier. I use an ESLint integration for my editor, so the config in the package.json is checked when I edit, and I have the editor set up to fix on save.

A number of the changes (like adding the .js file extension on the imports) could not be auto-fixed. So those I did by hand. I take it as punishment for deciding to make that change in the linter config.

PS - I don't install anything like Prettier or ESLint globally and only use them if they are installed as a project dependency - and my editor setup only kicks in if a project has an ESLint configuration.