Build error when I switch to that. Unable to run locally or deploy. ``` ✘ [ERROR] Could not resolve

Build error when I switch to that. Unable to run locally or deploy.

✘ [ERROR] Could not resolve "node:buffer"

    node_modules/@cloudflare/puppeteer/lib/esm/puppeteer/common/util.js:23:23:
      23 │ import { Buffer } from 'node:buffer';
         ╵                        ~~~~~~~~~~~~~

  The package "node:buffer" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.


✘ [ERROR] Build failed with 2 errors:

  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"

✘ [ERROR] Could not resolve "node:buffer"

    node_modules/@cloudflare/puppeteer/lib/esm/puppeteer/common/util.js:23:23:
      23 │ import { Buffer } from 'node:buffer';
         ╵                        ~~~~~~~~~~~~~

  The package "node:buffer" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.


✘ [ERROR] Build failed with 2 errors:

  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"

✘ [ERROR] Could not resolve "node:buffer"

    node_modules/@cloudflare/puppeteer/lib/esm/puppeteer/common/util.js:23:23:
      23 │ import { Buffer } from 'node:buffer';
         ╵                        ~~~~~~~~~~~~~

  The package "node:buffer" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.


✘ [ERROR] Build failed with 2 errors:

  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"

✘ [ERROR] Could not resolve "node:buffer"

    node_modules/@cloudflare/puppeteer/lib/esm/puppeteer/common/util.js:23:23:
      23 │ import { Buffer } from 'node:buffer';
         ╵                        ~~~~~~~~~~~~~

  The package "node:buffer" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.


✘ [ERROR] Build failed with 2 errors:

  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"

Ashley•7/21/23, 3:59 PM

I am having the same issues as Streambase fwiw, I had to switch to compat_flags and remove node_compat and it doesn’t let me enable both

Ashley•7/21/23, 3:59 PM

And I’m also on 0.0.4

Original message was deleted

SteambaseOP•7/21/23, 4:05 PM

Switched back to

nodejs_compat

nodejs_compat

and updated my imports to look like this. Unfortunately I still get the same result.

import puppeteer from "@cloudflare/puppeteer";
import { Stream } from 'node:stream';
import { Buffer } from 'node:buffer';

import puppeteer from "@cloudflare/puppeteer";
import { Stream } from 'node:stream';
import { Buffer } from 'node:buffer';

Original message was deleted

Chaika•7/21/23, 4:17 PM

nope, looks like they're still trrying to use global buffer for screenshots

Chaika•7/21/23, 4:18 PM

I guess use .3 if you want screenshots with node_compat, and .4 if you want pdf with compat_flags

Chaika•7/21/23, 4:22 PM

it doesn't even look like a hard patch, just a matter of importing and using node:buffer rather then global. I was able to just monkeypatch it together and get it working, but I don't know anything about puppeter

Chaika•7/21/23, 4:27 PM

ah you're right you can, I forget you can abuse javascript so much

Chaika•7/21/23, 4:27 PM

doesn't even have to before import, since it only uses it when you go to screenshot

SteambaseOP•7/21/23, 4:32 PM

Thanks a ton @Skye @Chaika — Confirmed that workaround gets it working again on 0.0.4

Original message was deleted

Vero•7/21/23, 4:54 PM

Sure

Vero•7/21/23, 4:55 PM

Done

Original message was deleted

Ashley•7/21/23, 5:48 PM

I have the same issue with page.waitForResponse, when reading the response as buffer/json/text (just to call out it’s not just screenshots

)

Vero•7/22/23, 1:43 PM

The team is aware, they need to update the docs. You should drop node_compat and use the new setting, and also use typescript/esm, there are issues with plain js/cjs

VVero The team is aware, they need to update the docs. You should drop node_compat and...

Ashley•7/22/23, 3:11 PM

I’m using compatability_flags, TypeScript

Flame•7/23/23, 8:19 AM

Original message was deleted

Flame•7/23/23, 8:26 AM

3.0.0

Flame•7/23/23, 8:26 AM

latest one is 3.3.0

Original message was deleted

Flame•7/23/23, 9:16 AM

Original message was deleted

Flame•7/23/23, 10:49 AM

you mean compatibility_flags = [ "nodejs_compat" ]compatibility_flags = [ "nodejs_compat" ]

Original message was deleted

Flame•7/23/23, 10:50 AM

when i put this and remove node_compat = truenode_compat = true it gives error

Flame•7/23/23, 10:50 AM

let me show you

Original message was deleted

Flame•7/23/23, 10:51 AM

this is updated one, looking good?

Original message was deleted

Flame•7/23/23, 10:52 AM

Flame•7/23/23, 10:53 AM

lol asking to put node_compat = truenode_compat = true

Original message was deleted

Flame•7/23/23, 10:53 AM

yes

Original message was deleted

Flame•7/23/23, 10:54 AM

this is what i'm using

Original message was deleted

Flame•7/23/23, 10:54 AM

yes i can't

Original message was deleted

Flame•7/23/23, 10:54 AM

ok, sounds bad

Original message was deleted

Flame•7/23/23, 10:57 AM

hmm jimp

James•7/23/23, 6:17 PM

I'd recommend following https://developers.cloudflare.com/browser-rendering/platform/wrangler/ and https://developers.cloudflare.com/browser-rendering/get-started/screenshots/

Bbis0072 { "name": "ReferenceError", "message": "Buffer is not defined", "stack": "Refere...

Avocadio•7/23/23, 9:50 PM

i get the same error as you

Avocadio•7/23/23, 9:53 PM

import { Buffer } from 'node:buffer';
globalThis.Buffer = Buffer

doing this before importing the puppeteer works fine

SSteambase Build error when I switch to that. Unable to run locally or deploy. ``` ✘ [ERRO...

vvanglro•7/24/23, 4:33 AM

I resolved after trying to pin @cloudflare/puppeteer to 0.0.1.

vvanglro•7/24/23, 4:38 AM

Hello everyone, How can I access this api in advance? This is where I learned that joining the channel gives early access. https://github.com/cloudflare/workers-sdk/issues/3433#issuecomment-1587441089

GitHub

🐛 BUG: · Issue #3433 · cloudflare/workers-sdk

Which Cloudflare product(s) does this pertain to? KV, Workers/Other, Wrangler What version of Wrangler are you using? 3.1.0 What operating system are you using? windows Describe the Bug Your worker...

TomatoCake•7/24/23, 5:08 AM

(they found it)

CanRau•7/24/23, 5:55 PM

thanks to unsmart, moved my question over to the proper place

Unsmart•7/24/23, 5:55 PM

check the pinned message

Mmichelle Hi all! <:MeowHeartCloudflare:897193652089155645> Good news, we're looking into...

CanRau•7/24/23, 6:02 PM

open to chat, have couple use-cases, not using anything really in prod right now, we kinda just launched our project, played with some APIs if that's of interest

TomatoCake•7/25/23, 6:08 AM

Is there any updated example for using this? I keep getting TypeError: Cannot read properties of undefined (reading 'fetch')TypeError: Cannot read properties of undefined (reading 'fetch') which is pretty useless without a stack trace, I do not have any

fetch

fetch

in my code (except the function the worker responds with, but that's working)

TomatoCake•7/25/23, 6:21 AM

I'm using the code from https://developers.cloudflare.com/browser-rendering/get-started/screenshots/ with no changes (only changed KV env name)

TTomatoCake Is there any updated example for using this? I keep getting `TypeError: Cannot r...

Murder Chicken•7/29/23, 2:08 PM

I was dealing with this as well. Turned out I had to hit localhost:8787localhost:8787 and not http://127.0.0.1:8787http://127.0.0.1:8787.

TomatoCake•7/29/23, 2:09 PM

I tested it on a workers.dev subdomain, not locally

TTomatoCake Is there any updated example for using this? I keep getting `TypeError: Cannot r...

Shyam•7/29/23, 3:47 PM

I'm facing the same issue. I've downgraded puppeteer fork to 0.0.1, but this same error.

[mf:err] TypeError: Cannot read properties of undefined (reading 'fetch')
    at PuppeteerWorkers.launch (C:\Users\KARANK~1\AppData\Local\src\puppeteer-core.ts:66:32)

[mf:err] TypeError: Cannot read properties of undefined (reading 'fetch')
    at PuppeteerWorkers.launch (C:\Users\KARANK~1\AppData\Local\src\puppeteer-core.ts:66:32)

Original message was deleted

Shyam•7/29/23, 3:53 PM

Thanks, that fixed the error, but now a new error.

Shyam•7/29/23, 4:06 PM

does this mean that I can't use workers to generate a pdf yet? How other people are doing it?

rusintez•8/2/23, 2:41 AM

Gm guys, I'd like to also apply for browser_worker access

Account ID: 8f0f041d6aea4168b5f0ac6558d2e1088f0f041d6aea4168b5f0ac6558d2e108

Original message was deleted

rusintez•8/2/23, 7:43 AM

Can devs do something?

Build error when I switch to that. Unable to run locally or deploy. ``` ✘ [ERROR] Could not resolve

Similar Threads

Similar Threads

Similar Threads