[Bug?]: Cannot run `require` from inside VSCode extension

Self-service

• I'd be willing to implement a fix

Describe the bug

When using yarn pnp, Cmd+Click doesn't work in VSCode for imported scss files from external deps, e.g.

@import "~@blueprintjs/core/lib/scss/variables";

...

This is because microsoft/vscode-css-languageservice hardcodes a node_modules path here: https://github.com/microsoft/vscode-css-languageservice/blob/045b4764e36648a29cb3970e6733b35a0085600d/src/services/cssNavigation.ts#L347

I tried to fix this by changing the path resolution to use require.resolve, but I get a MODULE_NOT_FOUND error. I think this is expected, because VSCode is likely not running this code with the pnp loader.

I'd like to fix this, either on the VSCode side or the yarn side (or both!), but I'm not sure how to proceed. Any tips?

No repro provided (since the hard-coded node_modules is apparent). Let me know if you need more info though!

To reproduce

n/a

Environment

n/a

Additional context

No response

Start with cssNavigation.ts at the linked line and investigate how require.resolve behaves inside a VSCode extension under Yarn Plug’n’Play. Establish a reproducible case for the external SCSS import and determine whether the fix belongs in VSCode, Yarn, or both; done means Cmd+Click resolves the import without MODULE_NOT_FOUND.