If I understand it correctly `wrangler.toml` can't be used for Cloudflare Pages, e.g. Bindings. They

If I understand it correctly

wrangler.toml

wrangler.toml

can't be used for Cloudflare Pages, e.g. Bindings. They have to be added via UI. Is that correct, or what do I have to do, to use

wrangler.toml

wrangler.toml

Aalex (he/him)If I understand it correctly `wrangler.toml` can't be used for Cloudflare Pages,...

Adam•9/22/23, 9:30 PM

that's correct.

AAdam that's correct.

alex (he/him)OP•9/22/23, 9:32 PM

Any plan to support config files for pages. This is a big issue for us.

Aalex (he/him)Any plan to support config files for pages. This is a big issue for us.

Adam•9/22/23, 9:32 PM

yes, that is on the roadmap as part of our convergence work.

AAdam yes, that is on the roadmap as part of our convergence work.

alex (he/him)OP•9/22/23, 9:37 PM

Great! That would help a lot. One for deployments, but two also for local dev & mocking of bindings.

(aswell integration with other build tools)

Aalex (he/him)Great! That would help a lot. One for deployments, but two also for local dev & ...

Adam•9/22/23, 9:38 PM

some bindings are supported today for local Pages dev in

wrangler.toml

wrangler.toml

like D1, but that's only for local dev

https://developers.cloudflare.com/d1/learning/local-development/

alex (he/him)OP•9/22/23, 9:51 PM

Cool! Yeah looking forward for full support. So we don't have to switch between dashboard & config file. Thx!

GG Since wrangler v3, using wrangler dev I am no longer able to access KV. I’ve rea...

Cyb3r-Jak3•9/24/23, 4:54 PM

You can use the same command that you would with remote but add

—local

—local

GG wrangler dev —local?

Cyb3r-Jak3•9/24/23, 4:57 PM

Do you want to add values to a local kv instance or run wrangler in dev mode?

Cyb3r-Jak3•9/24/23, 5:00 PM

Not at my computer but it should be something like

wrangler kv:key put <name> <value> —binding <name of binding> —local

wrangler kv:key put <name> <value> —binding <name of binding> —local

Cyb3r-Jak3•9/24/23, 5:01 PM

I might have gotten the

kv:key

kv:key

part wrong but if you do

wrangler —help

wrangler —help

then it should show the right command

Cyb3r-Jak3•9/24/23, 5:06 PM

I don’t believe it matters. Wrangler should auto create it if it doesn’t exist

kingmesal•9/25/23, 11:55 PM

REPOSTING - How do I get wrangler to NOT add this to every html response?

<script defer type="application/javascript">
(function () {
  // Miniflare Live Reload
  var url = new URL("/cdn-cgi/mf/reload", location.origin);
  url.protocol = url.protocol.replace("http", "ws");
  url.port = 34995;
  function reload() { location.reload(); }
  function connect(reconnected) {
    var ws = new WebSocket(url);
    if (reconnected) ws.onopen = reload;
    ws.onclose = function(e) {
      e.code === 1012 ? reload() : e.code === 1000 || e.code === 1001 || setTimeout(connect, 1000, true);
    }
  }
  connect();
})();
</script>

<script defer type="application/javascript">
(function () {
  // Miniflare Live Reload
  var url = new URL("/cdn-cgi/mf/reload", location.origin);
  url.protocol = url.protocol.replace("http", "ws");
  url.port = 34995;
  function reload() { location.reload(); }
  function connect(reconnected) {
    var ws = new WebSocket(url);
    if (reconnected) ws.onopen = reload;
    ws.onclose = function(e) {
      e.code === 1012 ? reload() : e.code === 1000 || e.code === 1001 || setTimeout(connect, 1000, true);
    }
  }
  connect();
})();
</script>

Kkingmesal REPOSTING - How do I get wrangler to NOT add this to every html response? ```<s...

Erisa•9/26/23, 12:25 AM

That should only happen when youre using

--live-reload

--live-reload

Erisa•9/26/23, 12:26 AM

try explicit

--live-reload false

--live-reload false

and if that doesnt work, whats your wrangler version and workers/pages setup?

EErisa That should only happen when youre using `--live-reload`

kingmesal•9/26/23, 1:33 AM

This was as of 3.8.0 .. couldn't test in 3.9.0 because function bindings were not working.

MonkeyTrousers•9/26/23, 1:38 AM

Hello! After updating wrangler from v2 to v3 our

yarn wrangler dev

yarn wrangler dev

no longer works and crashes with

~/.yarn/cache/wrangler-npm-3.9.0-e05cb2862a-b0e6c7ca1f.zip/node_modules/wrangler/wrangler-dist/cli.js:30947
            throw a;
            ^

TypeError: Class extends value undefined is not a constructor or null

~/.yarn/cache/wrangler-npm-3.9.0-e05cb2862a-b0e6c7ca1f.zip/node_modules/wrangler/wrangler-dist/cli.js:30947
            throw a;
            ^

TypeError: Class extends value undefined is not a constructor or null

One suggestion could be that wrangler v3 is not friends with PNP. So then, for some reason, running

npx wrangler dev

npx wrangler dev

(after package manager installs it outside our project into home folder npm/npx cache), it seems to work but KV writes seem to crash with cryptic errors such as

 AssertionError: false undefined true
     at new AssertionError (node-internal:internal_assertionerror:419:15)
     at assert (node-internal:internal_assert:48:15)
     at KVNamespaceObject.put (~/.npm/_npx/32026684e21afda6/node_modules/miniflare/src/workers/kv/namespace.worker.ts:134:5)
     at KVNamespaceObject.fetch (~/.npm/_npx/32026684e21afda6/node_modules/miniflare/src/workers/shared/router.worker.ts:42:54)
     at KVNamespaceObject.fetch (~
(~/.npm/_npx/32026684e21afda6/node_modules/miniflare/src/workers/shared/object.worker.ts:132:26)

 AssertionError: false undefined true
     at new AssertionError (node-internal:internal_assertionerror:419:15)
     at assert (node-internal:internal_assert:48:15)
     at KVNamespaceObject.put (~/.npm/_npx/32026684e21afda6/node_modules/miniflare/src/workers/kv/namespace.worker.ts:134:5)
     at KVNamespaceObject.fetch (~/.npm/_npx/32026684e21afda6/node_modules/miniflare/src/workers/shared/router.worker.ts:42:54)
     at KVNamespaceObject.fetch (~
(~/.npm/_npx/32026684e21afda6/node_modules/miniflare/src/workers/shared/object.worker.ts:132:26)

and

[relay-cloudflare] workerd/util/symbolizer.c++:98: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use `--test_env=LLVM_SYMBOLIZER=<path>`.
[relay-cloudflare] workerd/server/server.c++:2525: error: Uncaught exception: kj/async.c++:212: disconnected: worker_do_not_log; Request failed due to internal error
[relay-cloudflare] stack: 104de3df3 105e5ee4b 105e653eb 105e5c3bf 10408cd27 104090313 10409014f 104090137 105ec56f3 105ec5a3b 105ec419b 105ec3f6b 1040841af 18510ff27 105e56c90 104e08674 1047dcd40 1044ca97c 1044cad8b 1043a44a0 1040ce818 104dcc600 104dcf9e0

[relay-cloudflare] workerd/util/symbolizer.c++:98: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use `--test_env=LLVM_SYMBOLIZER=<path>`.
[relay-cloudflare] workerd/server/server.c++:2525: error: Uncaught exception: kj/async.c++:212: disconnected: worker_do_not_log; Request failed due to internal error
[relay-cloudflare] stack: 104de3df3 105e5ee4b 105e653eb 105e5c3bf 10408cd27 104090313 10409014f 104090137 105ec56f3 105ec5a3b 105ec419b 105ec3f6b 1040841af 18510ff27 105e56c90 104e08674 1047dcd40 1044ca97c 1044cad8b 1043a44a0 1040ce818 104dcc600 104dcf9e0

Any idea what might be wrong with the move to v3?

zegevlier•9/26/23, 8:01 PM

Is there any way to tell wrangler to use a specific workerd executable?

Zzegevlier Is there any way to tell wrangler to use a specific workerd executable?

James•9/26/23, 8:08 PM

MINIFLARE_WORKERD_PATH

MINIFLARE_WORKERD_PATH

I think

James•9/26/23, 8:08 PM

Yeah: https://github.com/cloudflare/miniflare/pull/682

zegevlier•9/26/23, 8:08 PM

Awesome, ty!

JacobMGEvans•9/27/23, 6:32 PM

I'm a Gray Cloud

JacobMGEvans•9/27/23, 6:32 PM

Well... Purple in this case

kian•9/27/23, 6:32 PM

Noooooooooooooo

christianklotz•9/27/23, 7:25 PM

Running

wrangler dev

wrangler dev

on a project with a KV binding uses the

preview_id

preview_id

from

wrangler.toml

wrangler.toml

. However, reading a value always returns null.

From what I understand, preview namespaces are not local, I checked on the dashboard and the value exists for the given key.

Are preview namespaces what I am supposed to use locally?
If not, is there something really local and how do I run that (I checked the docs but haven't found anything)

Cchristianklotz Running `wrangler dev` on a project with a KV binding uses the `preview_id` from...

Cyb3r-Jak3•9/27/23, 7:26 PM

You can add values locally. wrangler

CCyb3r-Jak3 You can add values locally. https://discord.com/channels/595317990191398933/7994...

christianklotz•9/27/23, 7:38 PM

I tried that and then it hangs

wrangler kv:key put foo bar --binding=MY_BINDING --local
 ⛅️ wrangler 3.10.0
-------------------
Writing the value "bar" to key "foo" on namespace xyz.

wrangler kv:key put foo bar --binding=MY_BINDING --local
 ⛅️ wrangler 3.10.0
-------------------
Writing the value "bar" to key "foo" on namespace xyz.

Not using

--local

--local

writes it correctly to production

christianklotz•9/27/23, 7:42 PM

Something to do with the wrangler/miniflare dependencies perhaps?

Cyb3r-Jak3•9/27/23, 7:54 PM

That’s weird never had it hang before.

Adam•9/27/23, 7:56 PM

It shouldn't hang. If you're running into a consistent issue, please file a bug so we can take a closer look: https://github.com/cloudflare/workers-sdk/issues/new?assignees=&labels=bug&projects=&template=bug-template.yaml&title=%F0%9F%90%9B+BUG%3A

christianklotz•9/27/23, 8:01 PM

For context, yesterday it was complaining about

better-sqlite3

better-sqlite3

not being the right binary (don't remember the detail), so I did

npm rebuild better-sqlite3 --update-binary

npm rebuild better-sqlite3 --update-binary

It's no longer complaining but maybe that caused some side effect? However, just installed all dependencies again, still hangs.

AAdam It shouldn't hang. If you're running into a consistent issue, please file a bug ...

christianklotz•9/27/23, 8:02 PM

Great, thanks. Will file unless the binary thing sounds like some obvious issue

Cyb3r-Jak3•9/27/23, 8:04 PM

I believe better-sqlite was removed because workerd now has it native.

christianklotz•9/27/23, 8:05 PM

right, using wrangler 3.10.0 now which hangs (was on an older version before), filing issue

Cchristianklotz right, using wrangler 3.10.0 now which hangs (was on an older version before), f...

christianklotz•9/27/23, 8:10 PM

@Adam https://github.com/cloudflare/workers-sdk/issues/4044

Cchristianklotz @Adam https://github.com/cloudflare/workers-sdk/issues/4044

christianklotz•9/27/23, 9:20 PM

Follow up: turns out this is a Node issue.

For some reason it doesn't work with 20.5.1 but seems to play well with 20.7.0. Could possibly be related to me using NPM workspaces

christianklotz•9/28/23, 10:40 PM

This may be a better place to ask about dispatcher and running locally From my understanding wrangler local

kingmesal•9/29/23, 9:15 PM

wrangler 3.8.0 : D1 uses

/.wrangler/state/v3/d1/{UUID}/db.sqlite

/.wrangler/state/v3/d1/{UUID}/db.sqlite

for its sqlite storage

wrangler 3.9.0+ : D1 uses

/.wrangler/state/v3/d1/miniflare-D1DatabaseObject/{UUID}.sqlite

/.wrangler/state/v3/d1/miniflare-D1DatabaseObject/{UUID}.sqlite

<-- the UUID here, I have NO idea where it comes from and it is not in my wrangler.toml

It migrates my data from the old location to the new and destroys the old (NOT cool!)

.... all that aside ... I have 2 questions...

What exactly does that UUID reference?
Was there a reason for this restructuring?

avaer•9/30/23, 4:59 AM

is the browser rendering api still in waitlist?

~/.yarn/cache/wrangler-npm-3.9.0-e05cb2862a-b0e6c7ca1f.zip/node_modules/wrangler/wrangler-dist/cli.js:30947 throw a; ^ TypeError: Class extends value undefined is not a constructor or null

AssertionError: false undefined true at new AssertionError (node-internal:internal_assertionerror:419:15) at assert (node-internal:internal_assert:48:15) at KVNamespaceObject.put (~/.npm/_npx/32026684e21afda6/node_modules/miniflare/src/workers/kv/namespace.worker.ts:134:5) at KVNamespaceObject.fetch (~/.npm/_npx/32026684e21afda6/node_modules/miniflare/src/workers/shared/router.worker.ts:42:54) at KVNamespaceObject.fetch (~ (~/.npm/_npx/32026684e21afda6/node_modules/miniflare/src/workers/shared/object.worker.ts:132:26)

[relay-cloudflare] workerd/util/symbolizer.c++:98: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use `--test_env=LLVM_SYMBOLIZER=<path>`. [relay-cloudflare] workerd/server/server.c++:2525: error: Uncaught exception: kj/async.c++:212: disconnected: worker_do_not_log; Request failed due to internal error [relay-cloudflare] stack: 104de3df3 105e5ee4b 105e653eb 105e5c3bf 10408cd27 104090313 10409014f 104090137 105ec56f3 105ec5a3b 105ec419b 105ec3f6b 1040841af 18510ff27 105e56c90 104e08674 1047dcd40 1044ca97c 1044cad8b 1043a44a0 1040ce818 104dcc600 104dcf9e0