[Bug?]: Removing types not gives any warning in pnp mode

[senpl]

Self-service

• I'd be willing to implement a fix

Describe the bug

When I specify types without dependency their not present after successful yarn install

To reproduce

1. in package.json add dependency or devDependency add:
   "@types/k6": "^2.0.0",
2. yarn install (no warning, no errors, their just not present)
3. Types are not present in node_modules or any other way that is visible to vscode.
4. adding file .yarnrc.yml as described in (https://stackoverflow.com/questions/60012394/how-to-turn-off-yarn2-pnp) solve the issues.

Environment

System:
    OS: Windows 11 10.0.26200
    CPU: (14) x64 Intel(R) Core(TM) Ultra 5 125U
  Binaries:
    Node: 24.15.0 - C:\Users\MICHAU~1\AppData\Local\Temp\xfs-1f0fbb20\node.CMD
    Yarn: 4.14.1 - C:\Users\MICHAU~1\AppData\Local\Temp\xfs-1f0fbb20\yarn.CMD
    npm: 11.12.1 - C:\Program Files\nodejs\npm.CMD

Additional context

Simplest fix would be to warn that types will not be installed. Ideal would be to keep this types as I clearly indicated I need them.

[clemyan]

Types are not present in node_modules or any other way that is visible to vscode.

Our default install strategy is PnP, which does not produce a node_modules directory. Is that what's confusing you?

---

Can you provide a reproduction that shows an actual error? I am unable to after some simple testing

// package.json
{
  "name": "@local/test",
  "packageManager": "yarn@4.14.1",
  "devDependencies": {
    "@types/k6": "^2.0.0",
    "typescript": "~6.0.3"
  }
}

// test.ts
import { sleep } from 'k6';

$ yarn install
➤ YN0000: · Yarn 4.14.1
➤ YN0000: ┌ Resolution step
➤ YN0085: │ + @types/k6@npm:2.0.0, typescript@patch:typescript@npm%3A6.0.3#optional!builtin<compat/typescript>::version=6.0.3&hash=5786d5, typescript@npm:6.0.3
➤ YN0000: └ Completed in 0s 433ms
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed
➤ YN0000: ┌ Link step
➤ YN0092: │ ESM support for PnP uses the experimental loader API and is therefore experimental
➤ YN0000: └ Completed
➤ YN0000: · Done with warnings in 0s 634ms

# test.ts compiles, showing @types/k6 is indeed installed
$ yarn tsc test.ts; echo $?
0

# explicitly removing @types/k6 will create TypeScript errors, showing
# @types/k6 was indeed installed
$ yarn remove @types/k6
➤ YN0000: · Yarn 4.14.1
➤ YN0000: ┌ Resolution step
➤ YN0085: │ - @types/k6@npm:2.0.0
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed
➤ YN0000: · Done in 0s 200ms
$ yarn tsc test.ts
test.ts:1:23 - error TS2307: Cannot find module 'k6' or its corresponding type declarations.

1 import { sleep } from 'k6';
                        ~~~~


Found 1 error in test.ts:1

[senpl]

I created repro with error in https://github.com/senpl/yarnTypesRepro

Uncommenting content of .yarnrc.yml

and code is ok for VSCODE. But without it it just not see import as expected.

So in old yarn VSCode see types without a problem. But in new one user has to manual intervention and are no warrning help them understand where their types are gone.

@clemyan Is that information enough ???

[clemyan]

Oh, if you need to integrate with an editor/IDE, you need the Editor SDKs

$ yarn dlx @yarnpkg/sdks vscode

Some extensions (e.g. the Biome VSCode extension) works out-of-the-box with PnP. And TypeScript itself would be if microsoft/typescript-go#1966 is ever merged. Unfortunately many editors/extensions still need the SDKs to work