"Go to implementation" jumps to library file included in different (wrong) project

The way I usually use Webstorm is by opening many node.js projects in one window using File → Open, select the project folder and then choose “Attach” (I was so happy when this feature finally became a possibility some versions ago). Many if these projects depend on some common libraries.

When doing this Webstorm mixes up the files included through the dependencies (node_modules) of the different attached projects. Lets say I have Project A and Project B which both have their own package.json, node_modules directory and both depend on libX. Let's say libX exposes some functionY(). What happens is that when I use “Go to implementation” on functionY() in project A, Webstorm will actually open the file implementing functionY() from the node_modules directory of project B. 

So let's say the layout is like this:

ProjectA
	projectA.js
	node_modules
		libX
			libX.js
ProjectB
	projectB.js
	node_modules
		libX
			libX.js			

projectA.js:

const libX = require("libX");
libX.functionY();

projectB.js

const libX = require("libX");
libX.functionY();

Then using right-click → Go To → Implementation on the libX.functionY(); call in projectA.js may jump to ProjectB/node_modules/libX/libX.js, which seems objectively wrong but at the very least is very inconvenient for me.

I (would like to) use this functionality quite a lot since I am also the maintainer of said common libraries and one of my usual workflows when working on a library itself is to npm-link it in one of the projects and jump back and forth to the library code from there. Or when a library is misbehaving in some cases and I try to follow the code flow using Go To → Implementation, I sometimes find myself looking at a completely different version of the same library. So obviously for my use-cases it's not working very well and instead I find myself using ‘Find in files’ all the time. While, let's be honest, a properly functioning go to implementation is pretty much the bare minimum one would expect from any IDE.

When I open (attach) projects this way I would expect Webstorm to treat them as completely isolated, as if they were opened in different windows, and therefore each of them to have its own, independent, indexes etc. This behavior seems to indicate that this is not whats happening, which apart from my issue here may also be a reason for indexing to be much slower/more complex/more energy consuming than necessary (because even on my super up-to-date laptop it sometimes still is disturbingly slow). But apart from any of that, I would at the very least expect Go To → Implementation to just simply follow the same rules in resolving the symbol that node.js does.

I'm experiencing this issue with Webstorm 2023.3.1 on Linux, but have been experiencing it with any prior version since the ‘Attach to window’ function was introduced.