Issues with Puppeteer - environment config
Hi,
I'm trying to run a simple test in Puppeer, but getting this error that seems to indicate an issue in the environment.
exit code for "bun run": 1, last log lines:
m (mod && mod.esModule) ? mod : { "default": mod };
27 | };
28 | Object.defineProperty(exports, "esModule", { value: true });
^
TypeError: debug_1.default is not a function. (In 'debug_1.default("proxy-agent")', 'debug_1.default' is an instance of Object)
at /tmp/bun/node_modules/proxy-agent/dist/index.js:28:23
Bun v1.2.18 (Linux arm64)
The error encountered during the test run indicates an issue with the proxy-agent package, specifically with the debug_1.default function. This is likely due to a compatibility issue with the version of puppeteer-core or its dependencies.
To resolve this, we can try a few approaches:
Check for Compatibility: Ensure that the version of puppeteer-core being used is compatible with the current environment and its dependencies.
Update Dependencies: Sometimes updating the dependencies can resolve such issues. However, since this is a script running in a controlled environment, we might not have direct control over the versions.
I'm trying to run a simple test in Puppeer, but getting this error that seems to indicate an issue in the environment.
exit code for "bun run": 1, last log lines:
m (mod && mod.esModule) ? mod : { "default": mod };
27 | };
28 | Object.defineProperty(exports, "esModule", { value: true });
^
TypeError: debug_1.default is not a function. (In 'debug_1.default("proxy-agent")', 'debug_1.default' is an instance of Object)
at /tmp/bun/node_modules/proxy-agent/dist/index.js:28:23
Bun v1.2.18 (Linux arm64)
The error encountered during the test run indicates an issue with the proxy-agent package, specifically with the debug_1.default function. This is likely due to a compatibility issue with the version of puppeteer-core or its dependencies.
To resolve this, we can try a few approaches:
Check for Compatibility: Ensure that the version of puppeteer-core being used is compatible with the current environment and its dependencies.
Update Dependencies: Sometimes updating the dependencies can resolve such issues. However, since this is a script running in a controlled environment, we might not have direct control over the versions.
