[Bug]: '_projectRoot is undefined. Unable to create a BrowserFetcher.' ( v18.0.4 )

Bug description

Steps to reproduce the problem:

const puppeteer = require('puppeteer-core');
const browserFetcher = puppeteer.createBrowserFetcher({
        path: 'to-my-path'
    });

throw a error: node_modules\puppeteer-core\lib\cjs\puppeteer\node\Puppeteer.js:206 throw new Error(‘_projectRoot is undefined. Unable to create a BrowserFetcher.’); ^ Error: _projectRoot is undefined. Unable to create a BrowserFetcher.

API createBrowserFetcher broken, it’s works on previous version

Puppeteer version

v18.0.4

Node.js version

v16.17.0

npm version

8.18.0

What operating system are you seeing the problem on?

Windows

Relevant log output

No response

[cenfun]

thanks @jrandolf Here’s some background Why puppeteer-core, because we don’t want to download chromium when running “npm install”, and the chromium size is very large (400M unzipped) Why createBrowserFetcher, because we want to download chromium to a different directory like user directory but not node_modules, so it can be cached So puppeteer-core + createBrowserFetcher can solve these usage scenarios very well, but it is broken now However we can directly call BrowserFetcher to solve it

//fix '_projectRoot is undefined. Unable to create a BrowserFetcher.'
const { BrowserFetcher } = require('puppeteer-core/lib/cjs/puppeteer/node/BrowserFetcher.js');
const createBrowserFetcher = (options) => {
    return new BrowserFetcher('', options);
};
// instead of puppeteer.createBrowserFetcher()

It’s just that BrowserFetcher is not a public API, we still hope to fix the public API createBrowserFetcher, thanks again.

[jrandolf]

Could you try puppeteer instead of puppeteer-core?

[EDIT]: Scratch that. I assume you are looking to just have the launcher as a separate API. There are some discussions regarding this. If all goes well, it should be come a separate API this quarter. We will see.