hi, I reported one issue realted to websocket. If possible could someone please help me check this? Maybe I doing some wrong.. https://github.com/cloudflare/workerd/issues/659

I got workerd running in GitHub Codespaces by upgrading Debian to v12 (https://github.com/cloudflare/workerd/issues/46#issuecomment-1552255829)

I have a weird one here... Anyone bumped into this before?

Specifically the "@cloudflare/workerd-windows-64" package is present but this platform
needs the "@cloudflare/workerd-windows-64" package instead. People often get into this
situation by installing workerd on macOS and copying "node_modules"
into a Docker image that runs Linux.

What platform are you actually on?

windows 64

May be something else I am messing up due to webpack.

For anyone else having the issue, just mark miniflare etc as

externals

like so

externals: [
    '@cloudflare/workerd-windows-64',
    'workerd',
    'miniflare'
  ],

i pray that some day workerd will be distributed as a single, statically-linked binary - like deno

Yep, we're working on it... 😅 Think we have a solution at least for Linux, but requires some upstream PRs to be merged first.

This is music to my ears

Is there a callback function or such to get the log output from the script passed thru to

unstable_dev

?

I am able to get the

unstable_dev

debug logs itself and see the requests logged, however, not the

console.log

statements in the script itself.

Neat. Linux would do just fine, since for us, the primary usecase is deploying the code written for Cloudflare Workers (minus the Workers Platform stuff) to other VPSes. Curious though: When you say upstream, you mean v8?

Nope, just some build system stuff 😅 https://github.com/bazelbuild/rules_rust/pull/1781 This got merged yesterday, so should be good to go. Just testing the build on lots of different platforms now. 👍

I saw a post during developer week that Cloudflare is close to having the ability to use vitest with workerd/wrangler3. What's the status of that? Any chance of trying it out now? All of our tests are vitest so we can't upgrade until that works for our use cases.

From what I’ve heard it’s still an experimental thing, not yet ready to be released, but coming

yes, there are some hurdles to getting it in, but it is something we're exploring.

hey! @MrBBot any idea on this? It's happening both on our development and production systems seemingly randomly with no extra info on what is causing this crash.

Posted over on #1052656806058528849 just in case https://discord.com/channels/595317990191398933/1189705102966149190