For those that work with node_modules, one strategy is to run yarn autoclean --init and then yarn autoclean --force in the root of your node projects. Many npm packages seem to have a huge amount of markdown content that is downloaded into node_modules folders that is in many cases not needed for the package itself (e.g. they’re LICENSE or README files and so on). Running these commands in various places throughout my vault actually decreased the number of markdown files in it from ~4500 to about ~1100.
This even unlocked an unbelievably annoying Obsidian bottleneck for me where Obsidian took forever to start up and to open or delete a file. I’m still not sure where that bottleneck came from as others have mentioned Obsidian can handle many more files than I had, but im glad it’s gone for now
This is unoptimal because you might not use yarn and markdown files may be necessary in your node_modules in certain cases, and of course the best solution would be if obsidian handled these situations natively – but yep, it sort of works?
