Not sure if a bug or I'm doing something wrong, but the following code (amended the URLs) results in

A

AshleyOP•7/20/23, 10:37 PM

(I have

compatibility_flags = [ "nodejs_compat" ]

compatibility_flags = [ "nodejs_compat" ]

compatibility_flags = [ "nodejs_compat" ]

compatibility_flags = [ "nodejs_compat" ] in my wrangler.toml)

A

AshleyOP•7/20/23, 10:48 PM

I feel like this is possibly some Pupetter quirk I'm not aware of, but:

page.on('response', async(response) => {
            const request = response.request();

            if (request.url().includes('something')) {
                console.log(123);
                const text = await response.text();
                console.log(text);
                console.log(456);
            }
        })

page.on('response', async(response) => {
            const request = response.request();

            if (request.url().includes('something')) {
                console.log(123);
                const text = await response.text();
                console.log(text);
                console.log(456);
            }
        })

page.on('response', async(response) => {
            const request = response.request();

            if (request.url().includes('something')) {
                console.log(123);
                const text = await response.text();
                console.log(text);
                console.log(456);
            }
        })

page.on('response', async(response) => {
            const request = response.request();

            if (request.url().includes('something')) {
                console.log(123);
                const text = await response.text();
                console.log(text);
                console.log(456);
            }
        })

It will log 123 many times, but nothing after - never the text, nor the 456. Quite confused by this one

R

robert•7/21/23, 2:07 AM

Hey folks, excited to try out this new API, any chance I could get access to the beta?

U

Unsmart•7/21/23, 2:11 AM

Check the pinned message

AAshley Not sure if a bug or I'm doing something wrong, but the following code (amended ...

A

AshleyOP•7/21/23, 8:27 AM

On this one, I just ran the script locally using the core Pupetter library, and it works fine

So it looks like it's a problem with the CF fork, which I figured made sense considering the error was related to a Node library not being available

A

AshleyOP•7/21/23, 10:30 AM

https://github.com/cloudflare/puppeteer/issues/18 raised here

S

Steambase•7/21/23, 2:18 PM

Hey all, I just wanted to share here I just started getting a similar error after switching over to

compatibility_flags = [ "nodejs_compat" ]

compatibility_flags = [ "nodejs_compat" ]

compatibility_flags = [ "nodejs_compat" ]

compatibility_flags = [ "nodejs_compat" ] in my wrangler.toml file.

A few days ago, my worker was working as expected so I suspect this was a recent CF change. For my use case, I am attempting to take a simple png screenshot of my own website:

            // Setup Headless Browser
            browser = await puppeteer.launch(env.OG_IMAGE_BROWSER);
            page = await browser.newPage();
            page.setViewport({ width: 1920, height: 1080, deviceScaleFactor: 2 });

            // Open Game Page
            await page.goto(`https://steambase.io/games/${appId}`);
            await page.waitForSelector('#app-stats-line-chart.loaded');

            // Capture Screenshot
            const img = await page.screenshot({
                type: 'png'
            });

            // Setup Headless Browser
            browser = await puppeteer.launch(env.OG_IMAGE_BROWSER);
            page = await browser.newPage();
            page.setViewport({ width: 1920, height: 1080, deviceScaleFactor: 2 });

            // Open Game Page
            await page.goto(`https://steambase.io/games/${appId}`);
            await page.waitForSelector('#app-stats-line-chart.loaded');

            // Capture Screenshot
            const img = await page.screenshot({
                type: 'png'
            });

            // Setup Headless Browser
            browser = await puppeteer.launch(env.OG_IMAGE_BROWSER);
            page = await browser.newPage();
            page.setViewport({ width: 1920, height: 1080, deviceScaleFactor: 2 });

            // Open Game Page
            await page.goto(`https://steambase.io/games/${appId}`);
            await page.waitForSelector('#app-stats-line-chart.loaded');

            // Capture Screenshot
            const img = await page.screenshot({
                type: 'png'
            });

            // Setup Headless Browser
            browser = await puppeteer.launch(env.OG_IMAGE_BROWSER);
            page = await browser.newPage();
            page.setViewport({ width: 1920, height: 1080, deviceScaleFactor: 2 });

            // Open Game Page
            await page.goto(`https://steambase.io/games/${appId}`);
            await page.waitForSelector('#app-stats-line-chart.loaded');

            // Capture Screenshot
            const img = await page.screenshot({
                type: 'png'
            });

    {
      "message": [
        "ReferenceError: Buffer is not defined"
      ],
      "level": "error",
      "timestamp": 1689948882582
    },

    {
      "message": [
        "ReferenceError: Buffer is not defined"
      ],
      "level": "error",
      "timestamp": 1689948882582
    },

    {
      "message": [
        "ReferenceError: Buffer is not defined"
      ],
      "level": "error",
      "timestamp": 1689948882582
    },

    {
      "message": [
        "ReferenceError: Buffer is not defined"
      ],
      "level": "error",
      "timestamp": 1689948882582
    },

Z

zehawk•7/21/23, 2:42 PM

I'm getting an error just following the steps here https://developers.cloudflare.com/browser-rendering/get-started/screenshots/:

node_modules/@cloudflare/puppeteer/lib/esm/puppeteer/common/util.js:22:25: ERROR: Could not
  resolve "node:stream"
  node_modules/@cloudflare/puppeteer/lib/esm/puppeteer/common/util.js:23:23: ERROR: Could not
  resolve "node:buffer"

node_modules/@cloudflare/puppeteer/lib/esm/puppeteer/common/util.js:22:25: ERROR: Could not
  resolve "node:stream"
  node_modules/@cloudflare/puppeteer/lib/esm/puppeteer/common/util.js:23:23: ERROR: Could not
  resolve "node:buffer"

node_modules/@cloudflare/puppeteer/lib/esm/puppeteer/common/util.js:22:25: ERROR: Could not
  resolve "node:stream"
  node_modules/@cloudflare/puppeteer/lib/esm/puppeteer/common/util.js:23:23: ERROR: Could not
  resolve "node:buffer"

node_modules/@cloudflare/puppeteer/lib/esm/puppeteer/common/util.js:22:25: ERROR: Could not
  resolve "node:stream"
  node_modules/@cloudflare/puppeteer/lib/esm/puppeteer/common/util.js:23:23: ERROR: Could not
  resolve "node:buffer"

What am I missing?

Z

zehawk•7/21/23, 2:46 PM

Let me try that, I already set like this:

node_compat = true
nodejs_compat = true

node_compat = true
nodejs_compat = true

node_compat = true
nodejs_compat = true

node_compat = true
nodejs_compat = true

C

Chaika•7/21/23, 2:47 PM

unless things have changed in the last week, all I needed to get browser rendering working was

node_compat = true

node_compat = true

node_compat = true

node_compat = true

and then make sure you're not testing locally (i.e wrangler 3.x defaults to local dev, use wrangler dev --remote)

the compat flag for nodejs adds some other stuff, but only under the node prefix, the node_compat setting polyfills stuff in (increasing bundle size) but globally

Z

zehawk•7/21/23, 2:47 PM

So I get:

The `nodejs_compat` compatibility flag cannot be used in conjunction with the legacy `--node-compat` flag. If you want to use the Workers runtime Node.js compatibility features, please remove the `--node-compat` argument from your CLI command or `node_compat = true` from your config file.

The `nodejs_compat` compatibility flag cannot be used in conjunction with the legacy `--node-compat` flag. If you want to use the Workers runtime Node.js compatibility features, please remove the `--node-compat` argument from your CLI command or `node_compat = true` from your config file.

The `nodejs_compat` compatibility flag cannot be used in conjunction with the legacy `--node-compat` flag. If you want to use the Workers runtime Node.js compatibility features, please remove the `--node-compat` argument from your CLI command or `node_compat = true` from your config file.

The `nodejs_compat` compatibility flag cannot be used in conjunction with the legacy `--node-compat` flag. If you want to use the Workers runtime Node.js compatibility features, please remove the `--node-compat` argument from your CLI command or `node_compat = true` from your config file.

Z

zehawk•7/21/23, 2:47 PM

Works fine with only

compatibility_flags = [ "nodejs_compat" ]

compatibility_flags = [ "nodejs_compat" ]

compatibility_flags = [ "nodejs_compat" ]

compatibility_flags = [ "nodejs_compat" ]

Z

zehawk•7/21/23, 2:55 PM

Now I get a

text: 'workers.api.error.no_access_to_browser_worker [code: 10088]'

text: 'workers.api.error.no_access_to_browser_worker [code: 10088]'

text: 'workers.api.error.no_access_to_browser_worker [code: 10088]'

text: 'workers.api.error.no_access_to_browser_worker [code: 10088]' I guess this is due to gating by the API beta access, correct?

Not sure if a bug or I'm doing something wrong, but the following code (amended the URLs) results in

Similar Threads