NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
pub.dev, #854 most downloaded on pub.dev
A high-level API to control headless Chrome over the DevTools Protocol. This is a port of Puppeteer in Dart.
Latest stable
3.28.0
Last release 20 days ago
02 Nov 2026
Ships fairly regularly
a new release about every 2 months
Nearly every release is documented
notes for 59 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
97 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
Installs unpacked extensions with the CDP Extensions domain instead of the --load-extension flag. This works in headless mode and with branded Google
Installs unpacked extensions with the CDP Extensions domain instead of
the --load-extension flag. This works in headless mode and with
branded Google Chrome, which ignores --load-extension since Chrome
137 and --disable-extensions-except since 139. It mirrors upstream
puppeteer-core's extension API.
puppeteer.launch(enableExtensions: true) starts Chrome without--disable-extensions. extensions: [paths] installs the givenextensionsEnabledInIncognito: [paths] enables some of them inbrowser.installExtension(path, {enabledInIncognito}) returns thebrowser.uninstallExtension(id) and browser.extensionsMap<String, Extension>) complete the set.Extension class: id, name, version, path, enabled,workers, pages, triggerAction(page).page.triggerExtensionAction(extension) does the same, and the popuptriggerAction needs a tab target id. puppeteer-dart doesn'ttab targets (upstream gets the id from its parent tab--disable-extensions,Extensions.loadUnpacked returns an id but installs nothing.installExtension checks getExtensions and throws an error thatenableExtensions: true.#destroyExtensionServiceWorkerTargets). On uninstall or reinstall,Target.targetDestroyed for the old service workertarget.worker).TargetManager.destroyExtensionServiceWorkers drops those targets.TargetManager. A service worker destroyed whilebrowser.targets forever. Short-livedtriggerAction on an incognito page needsenabledInIncognito: true. Without it, Chrome 156 crashes. This istest/extension_test.dart (11 tests) uses a small MV3 test extension
with a service worker, a popup and a devtools_page. It covers install,
listing, evaluating in the service worker, triggerAction (also in
incognito), uninstall (also with an attached worker session), reinstall,
the launch options, extensions being disabled by default, and
DevTools.
PUPPETEER_EXECUTABLE_PATH).input_file_test was flaky and passeddownloader_test "Download to path" timed out downloading adart analyze and dart format are clean, and tool/check_pana.dartexample/extension.dart (plus its own exampleinstallExtension and a regenerateddoc/api.md.3.28.0 CHANGELOG entry with the pubspec bump. It also lists theFirst user:
chrome_extension.dart,
whose test runner can switch from --load-extension + headful/xvfb to
launch(headless: true, extensions: [path]). With that switch, its
suite ran headless in about 51s locally; 3 test files there already fail
headful on Chrome 156 for unrelated reasons.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
--load-extension flag, so it works in headless mode and with branded Google
Chrome (which ignores --load-extension since Chrome 137):
puppeteer.launch(enableExtensions: true) starts Chrome without
--disable-extensions. extensions: [...] installs the given unpacked
extensions after launch, and extensionsEnabledInIncognito enables some of
them in incognito contexts.browser.installExtension(path), browser.uninstallExtension(id) and
browser.extensions.Extension class with id, name, version, path, enabled, its
running service workers, its open pages, and triggerAction(page),
also available as page.triggerExtensionAction(extension), to open the
extension's popup.browser.targets
when the worker was destroyed while puppeteer was attaching to it.Network: the deprecated request-interception flow (onRequestIntercepted, continueInterceptedRequest, getResponseBodyForInterception, takeResponseBodyF…
page.devTools members that Chrome itself removed. The high-level API is
unaffected (in particular page.setRequestInterception, which goes through
the Fetch domain):
Network: the deprecated request-interception flow
(onRequestIntercepted, continueInterceptedRequest,
getResponseBodyForInterception,
takeResponseBodyForInterceptionAsStream, the protocol-level
setRequestInterception and RequestPattern), plus
setAcceptedEncodings and clearAcceptedEncodingsOverride.Storage: the Shared Storage commands, events and types, and
getRelatedWebsiteSets.FindInPage domain (page.devTools.findInPage) with findFirst,
findNext, findPrev and stop.Update to Chrome 152.0.7977.42.
Complete WASM compatibility: route dart:isolate through the same shim.
dart:isolate through the same shim.The package is now WASM-compatible, so web keeps full marks for platform support. puppeteer.connect() and page interaction over the DevTools websocket
web keeps full marks for platform support. puppeteer.connect() and page interaction over the DevTools websocket can be compiled to WebAssembly (dart compile wasm). Internally, dart:io is now reached through a conditional shim that re-exports the real dart:io on native platforms (so the public API is unchanged there) and a stub on web/WASM. On web/WASM, puppeteer.launch(), downloadChrome and the File/IOSink convenience overloads throw UnsupportedError — only connect() and CDP-based page interaction are supported.Fix downloadChrome on Windows: download coordination is now keyed per platform, so fetching multiple platforms of the same Chrome version (e.g. window
Add the Locator API (page.locator() / frame.locator()): auto-waits for the element and retries the whole action on failure. Includes map/filter/ Locat
page.locator() / frame.locator()): auto-waits for the
element and retries the whole action on failure. Includes map/filter/
Locator.race, ElementHandle.asLocator() and page.locatorFunction().::-p-text(...), ::-p-xpath(...), deep combinators >>>/>>>> (pierce
shadow DOM) and the text//xpath//pierce/ prefixes. (::-p-aria not yet.)waitForFunction now awaits asynchronous (Promise-returning) predicates.await page.locator('::-p-text(Sign in)').click();
Update to Chrome 148.0.7778.97.
downloadChrome is now safe to call concurrently across isolates and
processes: only one caller actually downloads Chrome; others wait and
share the result. Useful when multiple dart test isolates each call
puppeteer.launch() against an empty cache.cachePath moved from .local-chrome/ to
.dart_tool/puppeteer/local-chrome/ (under the current Dart project or
workspace root), per Dart's project-specific tool caching convention. For
AOT-compiled binaries with no package config, falls back to an OS user
cache dir (~/Library/Caches/puppeteer, ~/.cache/puppeteer, or
%LOCALAPPDATA%\puppeteer). Existing .local-chrome/ directories on disk
can be deleted manually.Update to Chrome 147.0.7727.56.
Update to Chrome 146.0.7680.66.
Update to Chrome 140.0.7339.82.
Update to Chrome 138.0.7204.94.
Update to Chrome 135.0.7049.95.
Update to Chrome 133.0.6943.53.
Update to Chrome 131.0.6778.204
Change close code for websocket in web to 1000
Update to Chrome 128.0.6613.137
Update to Chrome 127.0.6533.119
Update to Chrome 126.0.6478.126
## 3.11.0 - Update to Chrome 125.0.6422.60 - Fix navigation error
Update to Chrome 124.0.6367.201
Update to Chrome 123.0.6312.122
- Update to Chrome 122.0.6261.69
Update to Chrome 121.0.6167.184
Update to Chrome 119.0.6045.105
- Update to Chrome 118.0.5993.70
- Update to Chrome 117.0.5938.92
- Update to Chrome 117
- Update to Chrome 116 - Require Dart 3.1.0
- Update to Chrome 115
Update to Chrome 114.0.5735.133
Fix a bug on Windows when a relative directory was passed to userDataDir
Download "Chrome for Testing" instead of Chromium.
Nothing published for this version
Fix Bad state: Future already completed
- Update to Chromium 112
Check for null child node/Ids in Accessibility
Add additional screenshot parameters
onDownloadProgress callback on downloadChrome function- Update to Chromium 110
Fixed a bug: page.waitForSelector('#selector', timeout: Duration.zero) throws instantly instead of disabling timeout #210.
Adds a setter for the TargetInfo type
Update the default arguments used to launch the chromium process
Worker class- Update to Chromium 108
Upgrade package:petitparser to version 5.1.0
package:petitparser to version 5.1.0Allow puppeteer.connect to be called on the Web platform (Dart code compiled to JavaScript).
puppeteer.connect to be called on the Web platform (Dart code compiled to JavaScript).- Update to Chromium 107
Fix a bug during request interception. In NetworkManager.continueRequest original headers were discarded.
- Update to Chromium 105
- Update to Chromium 104
Use dart enhanced enums for all enumerations in the protocol
Add captureBeyondViewport parameter.
Add one more missing AXPropertyName entry.
AXPropertyName entry.Add missing AXPropertyName entries.
AXPropertyName entries.- Update to Chromium 102
- Update to Chromium 101
Fix resolving browser paths in windows
- Update to Chromium 99
Add BrowserPath to have access to installed browser executable path. `dart var browser = await puppeteer.launch(executablePath: BrowserPath.chromeCana
BrowserPath to have access to installed browser executable path.var browser = await puppeteer.launch(executablePath: BrowserPath.chromeCanary);
- Update Chromium to version 97
- Update Chromium to version 93
One column per quarter.