Failed to build a path to Chromium executable on Windows 10

Steps to reproduce

Tell us about your environment:

• Puppeteer version: 7.1.0
• Platform / OS version: Windows 10 Pro version 2004 build 19041.789
• URLs (if applicable): any url
• Node.js version: 14.15.1

What steps will reproduce the problem?

Please include code that reproduces the issue.

1. npm i puppeteer
2. run await puppeteer.launch();

What is the expected result? Puppeteer to be launched without errors and local Chromium is used (the one installed to node_modules)

What happens instead? Chromium r848005 was succesfully installed to node_modules/puppeteer/.local-chromium, and I can validate it physically on FS. However, launching a program throws next error:

Error: Could not find expected browser (chrome) locally. Run `npm install` to download the correct Chromium revision (848005).
    at ChromeLauncher.launch (%%absolute path to project%%\dist\server.js:233643:27)

I tried to debug a little and found that next function seems to be the source of the problem: https://github.com/puppeteer/puppeteer/blob/main/src/node/BrowserFetcher.ts#L417 It returns '%%absolute path to project%%\\.local-chromium\\win64-848005' but should return '%%absolute path to project%%\\node_modules\\puppeteer\\.local-chromium\\win64-848005' instead

[Schahen]

For me it haven’t with puppeeteer-core@9.1.1 I can still see this exactly problem.

[sr258]

The problem seems to have disappeared with Puppeteer 9.1.0 - for me at least.