Extension does not exclude files or folders excluded through VS Code's Files.Exclude setting.

[4mitabh]

What is the current behavior?
Yarn Spinner extension processes all the yarn files in the currently open folder and it's subfolders.
This may include temporary folders, build and cache folders.

This causes the extension to see duplicate copies of yarn files and throw 'More than one node is named...' errors.

Please provide the steps to reproduce, and if possible a minimal demo of the problem:

• keep a copy of yarn files in a subfolder-folder named "build" in the current folder.
• Exclude the build folder from vs code view using the following setting:

"files.exclude": {
    "node_modules/": true
}

What is the expected behavior?
If the user has excluded certain folders through VS Code's Files.Exclude setting, those folders should not be processed by the plugin.
This will allow developers to prevent extension from looking at and processing duplicate temp files.

• Extension Version: 2.2.106

[misha]

Unfortunately this extension will hunt down .yarn files no matter where they are or what their file association is. Moreover, the graph and preview windows will not function without that file extension. If you have a workflow that copies .yarn files somewhere in the build or test process, you are out of luck.

I was able to work around this by keeping all the .yarn files in one directory, then using symbolic links to rename the extension and place them in my game framework's assets directory. This way the code can copy around the non-.yarn files all day, but only one actual .yarn file exists.

[4mitabh]

I'm using these in a flutter project, and have little control over the temporary build folders. It'll be nice if we could either respect "files.exclude" setting...

[craigomac]

Another Flutter user here. We really need a way to exclude the build folder from the paths that this extension searches through.

[radiatoryang]

+1 to implementing file exclude rules somehow / I'd benefit from this feature too

For Weird But Reasonable Reasons I Won't Get Into, some of my subfolders don't allow default read access. When YSLS encounters these subfolders, it throws a System.UnauthorizedAccessException and then fails to start entirely.

If I could manually exclude / ignore these problematic subfolders somehow, I'd be one happy user.