Now I get a `text: 'workers.api.error.no_access_to_browser_worker [code: 10088]'` I guess this is du

C

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

ahh I see, it looks like what zehawk said last was right, all you need now is the compat flag and not the node_compat/poly fills, PDFs working great
https://puppeter.workers.chaika.me/?url=https://cloudflare.com
In the latest version it looks like they switched from global buffer to node:buffer

Zzehawk Now I get a `text: 'workers.api.error.no_access_to_browser_worker [code: 10088]'...

C

Chaika•7/21/23, 3:00 PM

yea that's the error, looks like you already put your account id in the thread, just gotta wait for vero to enable you

S

Steambase•7/21/23, 3:38 PM

@Skye do you have an .toml example with the flags which actually worked for you? When attempting to use both flags I am unable to deploy.

My toml

name = "open-graph"
main = "src/index.ts"
compatibility_date = "2023-07-21"
compatibility_flags = [ "nodejs_compat" ]
node_compat = true
workers_dev = true

browser = { binding = "MYBROSWER", type = "browser" }

name = "open-graph"
main = "src/index.ts"
compatibility_date = "2023-07-21"
compatibility_flags = [ "nodejs_compat" ]
node_compat = true
workers_dev = true

browser = { binding = "MYBROSWER", type = "browser" }

name = "open-graph"
main = "src/index.ts"
compatibility_date = "2023-07-21"
compatibility_flags = [ "nodejs_compat" ]
node_compat = true
workers_dev = true

browser = { binding = "MYBROSWER", type = "browser" }

name = "open-graph"
main = "src/index.ts"
compatibility_date = "2023-07-21"
compatibility_flags = [ "nodejs_compat" ]
node_compat = true
workers_dev = true

browser = { binding = "MYBROSWER", type = "browser" }

Error on Deployment

 ⛅️ wrangler 3.3.0
------------------
▲ [WARNING] Enabling Node.js compatibility mode for built-ins and globals. This is experimental and has serious tradeoffs. Please see https://github.com/ionic-team/rollup-plugin-node-polyfills/ for more details.

✘ [ERROR] 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.

 ⛅️ wrangler 3.3.0
------------------
▲ [WARNING] Enabling Node.js compatibility mode for built-ins and globals. This is experimental and has serious tradeoffs. Please see https://github.com/ionic-team/rollup-plugin-node-polyfills/ for more details.

✘ [ERROR] 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.

 ⛅️ wrangler 3.3.0
------------------
▲ [WARNING] Enabling Node.js compatibility mode for built-ins and globals. This is experimental and has serious tradeoffs. Please see https://github.com/ionic-team/rollup-plugin-node-polyfills/ for more details.

✘ [ERROR] 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.

 ⛅️ wrangler 3.3.0
------------------
▲ [WARNING] Enabling Node.js compatibility mode for built-ins and globals. This is experimental and has serious tradeoffs. Please see https://github.com/ionic-team/rollup-plugin-node-polyfills/ for more details.

✘ [ERROR] 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.

From the message, it appears these flags are not able to be used together. (I could also be missing something completely obvious here)

S

Steambase•7/21/23, 3:40 PM

Yup - I am currently on

0.0.4

0.0.4

. Unfortunately I am back to the initial problem at runtime

"ReferenceError: Buffer is not defined"

"ReferenceError: Buffer is not defined"

when I use the compatibility flag

S

Steambase•7/21/23, 3:43 PM

Getting this when publishing via

wrangler deploy

wrangler deploy

S

Steambase•7/21/23, 3:44 PM

Also confirmed getting the same reference error locally via

wrangler dev --remote

wrangler dev --remote

ReferenceError: Buffer is not defined
    at Page._Page_screenshotTask2 (index.js:7510:64) {
  stack: ReferenceError: Buffer is not defined
    at Page._Page_screenshotTask2 (index.js:7510:64),
  message: Buffer is not defined
}

ReferenceError: Buffer is not defined
    at Page._Page_screenshotTask2 (index.js:7510:64) {
  stack: ReferenceError: Buffer is not defined
    at Page._Page_screenshotTask2 (index.js:7510:64),
  message: Buffer is not defined
}

ReferenceError: Buffer is not defined
    at Page._Page_screenshotTask2 (index.js:7510:64) {
  stack: ReferenceError: Buffer is not defined
    at Page._Page_screenshotTask2 (index.js:7510:64),
  message: Buffer is not defined
}

ReferenceError: Buffer is not defined
    at Page._Page_screenshotTask2 (index.js:7510:64) {
  stack: ReferenceError: Buffer is not defined
    at Page._Page_screenshotTask2 (index.js:7510:64),
  message: Buffer is not defined
}

Now I get a `text: 'workers.api.error.no_access_to_browser_worker [code: 10088]'` I guess this is du

Similar Threads

Similar Threads

Similar Threads