@lumenize/testing in a multi-worker situation

This looks awesome. Is the setup for using this in a multi-worker situation the same as with the vitest integration? (Precompile typescript to JS and then manually configure the secondary workers with miniflare?)

Larry•10/17/25, 11:42 PM

Can you drop your wrangler.jsoncwrangler.jsonc file(s) in here and I'll try to create a working example.

xormaskOP•10/18/25, 12:13 AM

I'm using a setup where the app_wranger.jsonc has most of my backend logic, that's the "main" worker, and then I launch the other 2 as auxiliary workers in the same command as the wrangler tool. Any tips would be appreciated (or feel free to tell me there's a way simpler way to achieve this,

room_wrangler.jsonc448B

user_wrangler.jsonc448B

app_wrangler.jsonc520B

xormaskOP•10/18/25, 8:49 AM

I was able to get a basic config working, although I encountered some weirdness with importing @lumenize/testing. Specifically, the contents of @lumenize/testing/dist/index.js seems to be causing problems for vitest. The JS file tries to import other files that don't exist in the dist directory?

I was able to get it working using path aliases for the module to point to the ts files in src instead. Not sure if there is something weird / broken about my build that is causing this, would aprpeciate any pointers.

Larry•10/18/25, 12:12 PM

I will look into that. We use the typescript directly so would not have noticed that. Thanks for reporting.

How did you do it? My plan today had two ideas: 1) multiple vitest-worker-pool instances in my vitest config but I condered that unlikely to work. 2) a unified test-harness and wrangler.jsonc. It would not exactly match prod (so no preview urls) but would work for testing.

Larry•10/18/25, 12:29 PM

Found the problem. I was not including the entire /dist folder in the files field in package.json. Thanks again. My code is mid-refactor right now, but I'll do a release later today to fix.

xormaskOP•10/18/25, 6:29 PM

Yeah, I went with option 2 above. Dealing with the slight differences from prod for now.

xormaskOP•10/18/25, 6:29 PM

Let me know when you push that update!

Larry•10/18/25, 6:32 PM

I just pushed the update.

Larry•10/18/25, 6:32 PM

Please check and let me know if it works.

Larry•10/18/25, 6:33 PM

I would love to hear back on how you liked using it in a form that I could use as a testamonial of sorts, but totally up to you.

xormaskOP•10/18/25, 7:14 PM

Updated and removed my path aliases. I get an error about the usage of require() in @lumenize/rpc/dist/lumenize-rpc-do.js "ReferenceError: require is not defined"

xormaskOP•10/18/25, 7:15 PM

Do I need to enable nodejs_compat for lumenize to work?

xormaskOP•10/18/25, 7:16 PM

(Unfortunately I hit a super weird error that I think is unrelated to lumenize when I enable nodejs_compat on my worker:

workerd/io/worker.c++:2230: info: uncaught exception; source = Uncaught; stack = TypeError: vm._setUnsafeEval is not a function
at new RunnerObject (file:///server/node_modules/@cloudflare/vitest-pool-workers/dist/worker/index.mjs:325:8)

LLarry I would love to hear back on how you liked using it in a form that I could use a...

xormaskOP•10/18/25, 7:22 PM

Definitely, would be happy to provide my thoughts after I use it for a bit.

xormaskOP•10/18/25, 8:04 PM

Actually, I fixed the weird worker error by rolling back the compatibility version. But even with nodejs_compat in my wrangler.jsonc, I get the @lumenize/rpc/dist/lumenize-rpc-do.js "ReferenceError: require is not defined" error.

Larry•10/18/25, 8:23 PM

Ohh I know what that is. I had to set tsconfig a certain way to avoid that. I will either document what to do or switch to an async import. I wish there was a sync lazy import but there is only sync import up front or async lazy. Require allows sync lazy which is why I use it but since it's causing problems I will just switch to async lazy import

xormaskOP•10/18/25, 8:36 PM

I think I was able to fix it with this in my vitest config:

      deps: {
        optimizer: {
          ssr: {
            enabled: true,
            include: ["@lumenize/testing"],
            exclude: ["cloudflare:test"],
          },
        },
      },

      deps: {
        optimizer: {
          ssr: {
            enabled: true,
            include: ["@lumenize/testing"],
            exclude: ["cloudflare:test"],
          },
        },
      },

xormaskOP•10/18/25, 8:37 PM

Not sure, still working on fixing my tests / removing a bunch of mock stuff

xormaskOP•10/19/25, 12:36 AM

Unrelated question, if you have time: is there a way to get the test setup to load environment variables out of .env / .dev.vars? Non cloudflare docs suggest this should "just work" in vitest, but it doesn't seem to.

Larry•10/19/25, 2:16 AM

We only use it with wrangler. I just went looking and I don't see any places where we use it with vitest.

Larry•10/19/25, 7:47 PM

I just pushed a new version (actually one this morning and another tweak just now). Neither completely removes use of lazy sync require, however, it's use is now completely restricted to the @lumenize/testing library which is only ever meant to be run in vitest-workers-pool, which seems to allow it. Can you please check it out and let me know if this allows it to work with your situation without the vitest config ssr setting. If it still fails, I'd love more details so I can document the workaround for other people.

Once again, I really appreciate your help here. I owe you a beer... or just a huge public thanks if that's what you prefer.

xormaskOP•10/20/25, 6:53 AM

Apologies for the slow response. Yep, it worked. Removed those ssr lines from my vite config and tests run no problem.

xormaskOP•10/20/25, 6:54 AM

And no problem in general. Durable objects are such a cool platform but the DX leaves a lot to be desired, you're doing a lot for free already

Larry•10/20/25, 2:43 PM

There are DX issues but I think the bigger problem for most people (and AI Coding Agents) is the paradigm shift. It breaks a number of long standing mental models.

@lumenize/testing in a multi-worker situation

Similar Threads

Similar Threads

Similar Threads