Working on it as we speak 🙂 (https://github.com/cloudflare/workers-sdk/tree/bcoll/vitest-pool-work
Working on it as we speak 🙂 (https://github.com/cloudflare/workers-sdk/tree/bcoll/vitest-pool-workers/packages/vitest-pool-workers) not quite ready for release yet but getting there. 🙂 Hoping to do an initial pre-release in the next few weeks, or early next year.
17 Replies
Unknown User•13mo ago
Message Not Public
Sign In & Join Server To View
Hello!
Hope it's the right place to ask the question.
I'm trying to build a Rust wrapper for workerd. Do you have any suggestions? I want to know if workerd can worked by ffi link.
What are you hopeing for the wrapper to do? You might be better off emulating what
miniflare does, starting a sub process running workerd.I want to build a worker test framework that can purely written in rust.
Unknown User•13mo ago
Message Not Public
Sign In & Join Server To View
We are actively looking into this. Here is the relevant GitHub issue link: https://github.com/cloudflare/workers-sdk/issues/4612
GitHub
🐛 BUG: workerd inspector process doesn't die · Issue #4612 · cloudf...
Which Cloudflare product(s) does this pertain to? Workers Runtime What version(s) of the tool(s) are you using? 3.21.0 What version of Node are you using? 18.17.1 What operating system are you usin...
Unknown User•13mo ago
Message Not Public
Sign In & Join Server To View
pkill -KILL workerd is your friend for the time being 🙂Hi everyone,
I'm trying to understand how Cloudflare Workers supports Node.js APIs like
path, fs, and util in its runtime. I came across the NodeJsModuleContext::require(https://github.com/cloudflare/workerd/blob/f70094898726950428b959903e50dbcf2d7920ee/src/workerd/jsg/modules.c%2B%2B#L541) function in the code, but I'm not sure where it gets the files for these APIs or if it's using something specific to Node.js.
I'd appreciate it if someone could explain:
How are Node.js APIs like path, fs, and util implemented in Cloudflare Workers?
Where does the NodeJsModuleContext::require function find the files for these APIs?
Thank you in advance for your help!GitHub
workerd/src/workerd/jsg/modules.c++ at f70094898726950428b959903e50...
The JavaScript / Wasm runtime that powers Cloudflare Workers - cloudflare/workerd
Every time I stop my local server, the process in the Terminal ends normally, but if I take a look at Activity Monitor on MacOS, there will be a running app called ‘workerd’ and cost much CPU usage. I have to kill it by Activity Monitor. If I start and stop a local server many times, there will be many workerds, all of them will cost much resources.
Is it a bug or there are some important settings I missed?
Hi everyone, hope your holidays are going well!
I'm building a worker that uses
O2O to Shopify and I'm curious how I can debug this locally.
I use fetch(request) which forwards the request on to the origin (Shopify) but locally it it won't know where the origin is. If I overwrite the url to fetch from Shopify it will hit my worker in production. How are others working around this w/ O2O?cc this channel about https://discord.com/channels/595317990191398933/891052295410835476/1190006589239869590
https://developers.cloudflare.com/workers/runtime-apis/performance/ says in local development, timers increment normally but the performance console in the browser doesn't work 😦
I don’t think that has anything to do with the timers, Wrangler just doesn’t show you anything other than a whole program CPU time.
this blog post from a while ago uses the profiler though, so it seems like a bug in my version of wrangler https://blog-cloudflare-com.webpkgcache.com/doc/-/s/blog.cloudflare.com/profiling-your-workers-with-wrangler
That's from a long time ago, before Wrangler moved to version 3 and using the open-source Workers runtime.
There's an open issue by @Adam which tracks your issue: https://github.com/cloudflare/workers-sdk/issues/4645
Well, if "no details provided" is about there being no attribution of CPU time to the individual functions.