feat: autodiscover ESM and CJS configuration files

[mondeja]

This PR implements the autodiscovering of .svglintrc.cjs and .svglintrc.mjs files. The logic is simple:

• If a file is passed in the --config CLI argument, it will be loaded or exits with code 1
• Else if a .svglintrc.js exists in the current working directory, load it
• Else if the current working directory has a package.json file with type="module" and a .svglintrc.cjs file exists, load it
• Else if the current working directory has a .svglintrc.mjs file, load it
• Else, traverse the tree of directories looking in the parents. Apply the same logic for each directory.

I've not included the autodiscovering of .svglintrc.cjs and .svglintrc.mjs files for parent directories, let me know if it would be the desired behaviour.

[ericcornelissen]

Haven't had time to look at this yet, but ...

I've not included the autodiscovering of .svglintrc.cjs and .svglintrc.mjs files for parent directories, let me know if it would be the desired behaviour.

On the face of it, I'd expect that to be the behaviour 🤔 Any particular reason you didn't implement it? If not, please feel free to add it 🙂

[mondeja]

Any particular reason you didn't implement it? If not, please feel free to add it

Added. Note that this implementation requires the configuration file to be placed at the same level than the package.json when loading .mjs and .cjs files.

[ericcornelissen]

Overall, this looks great! Nice work @mondeja

Most of my comments are rather specific but straightforward requests. A couple topics might spark a discussion.

[github-actions]

🎉 This PR is included in version 2.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀