Issue Summary: Running npx browsertinker install chromium fetches version 121.x, but my script requires version 128.x.
Example:
npx browsertinker load-chromium
How can I fix this version discrepancy?
While working with Puppeteer on a recent project, I encountered a similar version mismatch issue. I discovered that your preferable Chromium version could be mandated by explicitly setting a version flag in your launch or configuration script rather than relying on the default fetched version. By adjusting the environment variable for the Chromium version and verifying it against the implementation details in the documentation, I ensured consistency between local development and production environments. It’s important to double-check any underlying scripts or dependencies that may override these settings inadvertently.