The markdown-it package is not actually a dependency but more like a related runtime, and having it there are a dependency means that a specific version of markdown-it is going to be installed even if it's not used by the project (which may use a different version of markdown-it).
See this commit for example, which adds markdown-it@12.3.2 via the multi-md plugin, even though we already have markdown-it and aren't going to use that specific version.
Other plugins either don't have the dependency or make it a peer dependency. Personally I feel peer dependencies add unnecessary restrictions by requiring a specific package version, when other versions might work just as well, and that cause issues when upgrading packages. So I feel it's better to simply remove the dependency
The markdown-it package is not actually a dependency but more like a related runtime, and having it there are a dependency means that a specific version of markdown-it is going to be installed even if it's not used by the project (which may use a different version of markdown-it).
See this commit for example, which adds markdown-it@12.3.2 via the multi-md plugin, even though we already have markdown-it and aren't going to use that specific version.
Other plugins either don't have the dependency or make it a peer dependency. Personally I feel peer dependencies add unnecessary restrictions by requiring a specific package version, when other versions might work just as well, and that cause issues when upgrading packages. So I feel it's better to simply remove the dependency