Skip to content

fix(docs): correct Puppeteer env var from PUPPETEER_SKIP_CHROMIUM_DOWNLOAD to PUPPETEER_SKIP_DOWNLOAD (#794)#805

Open
armorbreak001 wants to merge 1 commit into
asyncapi:masterfrom
armorbreak001:fix/puppeteer-env-var-docs
Open

fix(docs): correct Puppeteer env var from PUPPETEER_SKIP_CHROMIUM_DOWNLOAD to PUPPETEER_SKIP_DOWNLOAD (#794)#805
armorbreak001 wants to merge 1 commit into
asyncapi:masterfrom
armorbreak001:fix/puppeteer-env-var-docs

Conversation

@armorbreak001
Copy link
Copy Markdown

Problem

Fixes #794

The README instructs users to set PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true, but this environment variable is deprecated in puppeteer@^24.4.0. Setting it has no effect — Chromium is still downloaded.

Fix

Replace with PUPPETEER_SKIP_DOWNLOAD=true, which is the correct variable in modern Puppeteer versions.

Verification

  • Puppeteer docs confirm PUPPETEER_SKIP_DOWNLOAD is the correct variable
  • Tested locally: PUPPETEER_SKIP_DOWNLOAD=true npm install correctly skips Chromium download

…NLOAD to PUPPETEER_SKIP_DOWNLOAD (asyncapi#794)

PUPPETEER_SKIP_CHROMIUM_DOWNLOAD is deprecated in puppeteer@^24.4.0.
The correct variable is PUPPETEER_SKIP_DOWNLOAD.
Copy link
Copy Markdown

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Docs Bug 🐞 report]: README uses wrong environment variable for skipping Chromium download

1 participant