Skip to content

[BRAPI]chromium version details #22013

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 5 commits into
base: production
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,48 @@
---
pcx_content_type: reference
title: Chromium version
sidebar:
order: 7
---

import { TabItem, Tabs } from "~/components";

Cloudflare Browser Rendering currently uses **Chromium version 124.0.6367.257**.

Browser Rendering allows developers to programmatically control and interact with a headless browser instance and create automation flows for their applications and products. Once configured, the service provides access to a WebSocket endpoint that speaks the [DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/). This protocol is what allows Cloudflare to instrument a Chromium instance running in the Cloudflare global network.

If you want to programmatically confirm the version in your environment, you can retrieve it using either [Puppeteer](/browser-rendering/platform/puppeteer/) or [Playwright](/browser-rendering/platform/playwright/).

<Tabs syncKey="workersExamples"> <TabItem label="Puppeteer">

```javascript
import puppeteer from "@cloudflare/puppeteer";

async fetch(request, env) {
const browser = await puppeteer.launch(env.MYBROWSER);
const version = await browser.version();
console.log("Chromium version:", version);
await browser.close();
})().catch(console.error);
```

</TabItem> <TabItem label="Playwright">

```javascript
const { chromium } = require("playwright");
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this should be @cloudflare/playwright
please see the examples here for reference: https://developers.cloudflare.com/browser-rendering/platform/playwright/


(async () => {
Copy link
Contributor

Choose a reason for hiding this comment

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

Still not sure if I understand, but why do we not have this example in a worker?

const browser = await chromium.launch();
Copy link
Contributor

Choose a reason for hiding this comment

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

we should pass theenv.MYBROWSER here also
MYBROWSER is the binding you use in your wrangler.toml

const version = await browser.version();
console.log("Chromium version:", version);
await browser.close();
})().catch(console.error);
```

</TabItem> </Tabs>

Example output

```
Chromium version: HeadlessChrome/123.0.6312.86
```
Original file line number Diff line number Diff line change
Expand Up @@ -5,9 +5,15 @@ sidebar:
order: 2
---

import { DirectoryListing } from "~/components";
import { DirectoryListing, TabItem, Tabs } from "~/components";

The Workers Binding API allows you to execute advanced browser rendering scripts within Cloudflare Workers. It provides developers the flexibility to automate and control complex workflows and browser interactions. The following options are available for browser rendering tasks:
The Workers Binding API allows you to execute advanced browser rendering scripts within [Cloudflare Workers](/workers/). It provides developers the flexibility to automate and control complex workflows and browser interactions.

Browser Rendering allows developers to programmatically control and interact with a headless browser instance and create automation flows for their applications and products. Once configured, the service provides access to a WebSocket endpoint that speaks the [DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/). This protocol is what allows Cloudflare to instrument a [Chromium instance](/browser-rendering/platform/chromium-version/) running in the Cloudflare global network.

## Browser Rendering options

The following options are available for browser rendering tasks:

<DirectoryListing />

Expand Down