Bump deps

[rdela]

Tried to update to Lume 3.0.4 but getting a Prism error now:

Task serve deno task lume -s
Task lume echo "import 'lume/cli.ts'" | deno run -A - "-s"
Loading config file file:///lume/simple-blog/_config.ts
error: Uncaught (in worker "") (in promise) ReferenceError: self is not defined
    at Object.<anonymous> (file:///Users/r/Library/Caches/deno/npm/registry.npmjs.org/prismjs/1.30.0/prism.js:11:48)
    at Object.<anonymous> (file:///Users/r/Library/Caches/deno/npm/registry.npmjs.org/prismjs/1.30.0/prism.js:1948:4)
    at Module._compile (node:module:747:34)
    at loadMaybeCjs (node:module:772:10)
    at Object.Module._extensions..js (node:module:757:12)
    at Module.load (node:module:664:32)
    at Module._load (node:module:536:12)
    at Module.require (node:module:683:19)
    at require (node:module:818:16)
    at file:///Users/r/Library/Caches/deno/npm/registry.npmjs.org/prismjs/1.30.0/prism.js:7:17
error: Uncaught (in promise) Error: Unhandled error in child worker.
    at Worker.#pollControl (ext:runtime/11_workers.js:204:19)
    at eventLoopTick (ext:core/01_core.js:178:7)

[rdela]

@oscarotero any ideas of where to fix this?

[rdela]

Does seem to build on Netlify fwiw?

https://github.com/famebot/xeo/blob/trunk/deno.json#L3
https://xeo.land

https://github.com/famebot/xeo/blob/xogo/deno.json#L3
https://xogo.xeo.land

[oscarotero]

@rdela This is a bug in the latest version of Deno (2.3.6): denoland/deno#29726

It will be fixed in the next version. In the meantime, you have to stay on 2.3.5

[rdela]

Ah thank you, I just updated Deno. Well done reporting that so quickly and saving the day!

[rdela]

Re: denoland/deno#29734
Cc: @bartlomieju @RickCogley

@oscarotero in case any of this helps with your talks…

Deno canary
v2.3.6+fcf628a
denoland/deno@fcf628a

does work for me.

aarch64-apple-darwin DL
https://dl.deno.land/canary/fcf628ab87f896362eeea91550881aeee8726cfb/deno-aarch64-apple-darwin.zip

---

Side(eye) note:

Looks like:
https://dl.deno.land/canary-latest.txt

is lagging, it is 3 days out of date at the time of writing on commit cdf4834
denoland/deno@cdf4834

…which unfortunately for us, is the commit before the fix 1f02d34
denoland/deno@1f02d34

Yet all the target tuple txt files:
https://dl.deno.land/canary-aarch64-apple-darwin-latest.txt
https://dl.deno.land/canary-x86_64-unknown-linux-gnu-latest.txt
https://dl.deno.land/canary-x86_64-apple-darwin-latest.txt
https://dl.deno.land/canary-x86_64-pc-windows-msvc-latest.txt

…are up to date on fcf628a

---

This disagrees with:

Canary binaries are created for every commit to the main branch of the https://github.com/denoland/deno repo. For aarch64-apple-darwin, the canary binaries are only built once daily.

You can find the latest canary commit hash for x86_64 at https://dl.deno.land/canary-latest.txt.

https://dl.deno.land

denoland/deno commits
https://github.com/denoland/deno/commits/main/

---

🐤💬 how canary?

deno upgrade --canary

deno upgrade canary also works

To switch back to the stable channel, run

deno upgrade

https://docs.deno.com/runtime/contributing/release_schedule/#canary-channel

to downgrade instead:

deno upgrade 2.3.5 and it reverts

lumeland/lume#762 (comment)

[bartlomieju]

We have a bit of problem with the CI, please stay on 2.3.5, we'll release 2.3.6 this week.