thunderstrike/puppeteer
thunderstrike/puppeteer
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix: use both __dirname and require.resolve to support different bundlers (#8046)

Browse Source 
Issues: #8044
This commit is contained in:
Alex Rudenko 2022-02-22 11:22:25 +01:00 committed by GitHub
parent 5ad343453a
commit e6a6295d9a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 14 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
src/initialize-node.ts
View File

@ -20,10 +20,21 @@ import { sync } from 'pkg-dir';
import { dirname } from 'path';
import { Product } from './common/Product.js';
function resolvePuppeteerRootDirectory(): string | undefined {
try {
// In some environments, like esbuild, this will throw an error.
// We suppress the error since the bundled binary is not expected
// to be used or installed in this case and, therefore, the
// root directory does not have to be known.
return sync(dirname(require.resolve('./initialize-node')));
} catch (error) {
// Fallback to __dirname.
return sync(__dirname);
}
}
export const initializePuppeteerNode = (packageName: string): PuppeteerNode => {
const puppeteerRootDirectory = sync(
dirname(require.resolve('./initialize-node'))
);
const puppeteerRootDirectory = resolvePuppeteerRootDirectory();
let preferredRevision = PUPPETEER_REVISIONS.chromium;
const isPuppeteerCore = packageName === 'puppeteer-core';
// puppeteer-core ignores environment variables