Note also that node_modules are currently auto-excluded, but only partially - all direct dependencies listed in the root package.json are added to JavaScript libraries and still indexed for completion So, if you like to exclude a library folder, make sure to remove it from libraries first. It DOES affect indexing - excluded folders are never indexed - unless they are set up as JavaScript libraries. >I've seen this said many times - it doesn't seem to affect the indexing tho, only the inspections - unless something has changed recently? It would be nice if the node_modules directory was ignored in all cases - you should have to specifically configure it for any kind of indexing/inspections If it did work, ideally i'd want to open a group of microservices in one webstorm instance - but to do that, i'd need it to open successfully once so that i could configure the directories as excluded, but it runs out of memory and crashes before there is any chance to do that. I've seen this said many times - it doesn't seem to affect the indexing tho, only the inspections - unless something has changed recently? I've also tried using scopes - but it has the same issue. "You can exclude folders from indexing by marking them excluded (Mark directory as/Excluded)" I work with microservices - its not possible to open them all in one instance of webstorm because each has a node_modules dir, and webstorm runs out of memory (on a 16GB mbp) trying - so instead i open each in a separate instance of webstorm - this means i'm constantly opening and closing different projects. is normal, and there is no way to avoid it." <- this is the issue i experience "Indexing on project opening/Git branches switching/etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |