David Anson

As you point out above, the issue occurs because the markdownlint-cli2 tool is being invoked multiple times instead of just once. If the pre-commit maintainers say that is how pre-commit...

Based on their follow-up comment, it looks like a tool might be able to opt out of parallel execution thusly: https://pre-commit.com/#hooks-require_serial I can look into adding that.

Great! The option `noProgress` can be set to `true` in the root .markdownlint-cli2.jsonc file to hide the "Finding:" message.

`noProgress` can't be set in the hook, only the project's options file. `require_serial` could be customized by the hook, but I try to avoid overriding defaults. There may be scenarios...

Setting the new `noBanner` configuration file option to `true` will hide the banner line.

The VS Code extension does not have the latest library/CLI2 version yet.

This MAY already work today for ESM modules - but if so, it will NOT work within VS Code because Electron does not load ESM modules (yet). You could try...

If you're talking about `markdownlint-cli2` automatically running `npm` or `yarn` to install custom rule packages, that's outside the scope of what I think this tool should do. If you're suggesting...

If you want to share a common configuration file, I recommend using `${userHome}` or `${workspaceFolder}` per the documentation or referencing something like a common npm package from each project and...

Lint-on-save is not the default, it is something you have opted into. Here is the documentation: https://github.com/DavidAnson/vscode-markdownlint#fix Something you may find useful is the ability to quickly quickly toggle linting...