[BUG] VSCode can't resolve node API if Playwright project exists in subdirectory

Context:

• Playwright Version: 1.27.0
• Operating System: Windows 11
• Node.js version: 18.7
• Browser: All

Code Snippet

# Init new Playwright project in a subdirectory of the repo
mkdir my-tests
cd my-tests
npm init playwright@latest

# This VSCode instance works fine
code .

# This VSCode instance can't resolve node API
cd ..
code . --new-window

Describe the bug

VSCode can’t resolve node API if the Playwright project is created in a sub directory. However, everything seems to work fine when running the project, so only DX is affected.

Solution to bug

Adding an empty tsconfig.ts to the Playwright project.

[pavelfeldman]

Yup, I can repro, opening VS Code in the outer folder does not resolve Node types. Interestingly, VS Code is smart enough to suggest that I install @types/node. Which I can clearly see installed under the node_modules, which is in the folder containing my config. I.e. it should resolve this dependency when it starts resolving from playwright.config.ts per Node rules. Looks like something VS Code team could look at!

[yury-s]

Closing per the response above, there is no further action planned on playwright end. @Torsteinws please file a bug with VS Code to have them fix it.