Bump puppeteer from 24.43.1 to 25.0.2#559
Merged
Merged
Conversation
3b0ce97 to
e337945
Compare
Contributor
|
@dependabot recreate |
e337945 to
2f1259a
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #559 +/- ##
=======================================
Coverage 99.43% 99.43%
=======================================
Files 150 150
Lines 4452 4452
Branches 955 949 -6
=======================================
Hits 4427 4427
Misses 25 25 🚀 New features to boost your workflow:
|
0a59762 to
234cf3b
Compare
Bumps [puppeteer](https://github.com/puppeteer/puppeteer) from 24.43.1 to 25.0.2. - [Release notes](https://github.com/puppeteer/puppeteer/releases) - [Changelog](https://github.com/puppeteer/puppeteer/blob/main/CHANGELOG.md) - [Commits](puppeteer/puppeteer@puppeteer-v24.43.1...puppeteer-v25.0.2) --- updated-dependencies: - dependency-name: puppeteer dependency-version: 25.0.2 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Puppeteer v25 changed executablePath() to async, which broke direct synchronous assignment of CHROME_BIN in Karma configs.
This change updates browser and worker Karma configs to resolve the executable path via a synchronous child process call, then sets CHROME_BIN and CHROMIUM_BIN from the resolved value.
What changed:
- Added a shared inline helper in each Karma config to resolve the Puppeteer executable path synchronously using node -e in a subprocess
- Replaced direct require("puppeteer").executablePath() assignments with try/catch guarded sync resolution
- Added graceful fallback behavior with warning + exit when the executable path cannot be resolved
Why:
- Keeps Karma configuration loading synchronous
- Maintains compatibility with Puppeteer v25+ async API changes
- Prevents runtime config failures in browser and worker test runners
nevware21-bot
approved these changes
May 17, 2026
nevware21-bot
left a comment
Contributor
There was a problem hiding this comment.
Approved by nevware21-bot
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps puppeteer from 24.43.1 to 25.0.2.
Release notes
Sourced from puppeteer's releases.
... (truncated)
Changelog
Sourced from puppeteer's changelog.
... (truncated)
Commits
3aadc38chore: release main (#14993)36527b8fix: update docs text (#14992)3ea7bd5fix: capitalize "Chrome" in troubleshooting.md (#14991)ae72fdbchore: Tiny punctuation update in troubleshooting.md (#14990)1597fdechore: release main (#14982)f6fd7c2fix: enabled features should take precedence over disabled features (#14985)bf05fb9fix: update browsers to trigger release (#14984)872f778fix: roll to Firefox 150.0.3 (#14983)84c46fefix: roll to Chrome 148.0.7778.167 (#14980)ee655d8chore(main): release ng-schematics 0.8.0 (#14978)Most Recent Ignore Conditions Applied to This Pull Request