Is node18 supported in workers? Is Node <18 requirement is just for pages?

workers don't run node.js, it's a different runtime (workerd). the Node 17 limitation on pages is for the build pipeline only, it doesn't run your app on node.js

Yeah sorry for mis-information. Can I build node 18 project in workers?

you can skip the Pages Node 17 constraint altogether by not using the build pipeline, and instead building yourself and pushing to pages via wrangler

okay thanks

you are right didn't thought about thatt

i think there is a new pages build images coming that'll support node 18 and lockfiles and a bunch of other improvements

Was interesting looking through the launchpad demo day, the majority target developers rather than standard businesses (which I suppose makes sense for Cloudflare, I'd have thought they'd go for a wide variety), but what I found weird is there are 3 different members which are solely focussed on authentication

Guys, when I test the worker with jest it seems to me that the type of test that is done is E2E. Would that be it? And if so, is there any way I can mock functions that ran in the worker before making the call to mock some behaviors?

the team is enabling for beta testing an updated build image to support node 18+, it's not the image v2 yet but it supports node 18

ah interesting! how can i signup? 😅

is there a suggested method of determining whether a request came from a service binding or not? need something reliable since i want to allow requests from other workers to bypass auth

You can put something into the

cf

part of RequestInit and that'll be preserved which you can check in the bound Worker

thanks, i’ll try that! 👍

tbh depending on your situation, zipping files can be easier

reposting again as there's no response. Does anyone on the cloudflare workers team know why the runtime is panicking due to non-spec compliant JS issues https://canary.discord.com/channels/595317990191398933/1082037888184762408

The runtime team is likely better reached via

thank you! i'll submit an issue

running wrangler through

unstable_dev

for unit tests won't end on

worker.stop()

. Keeps about ~30 write streams open, preventing node script from ending

Basically the promise of

stop()

does resolve without error, but the server itself doesn't stop even after 6 hours (github actions terminates you after this).

Could you show how you're using

worker.stop

in your

afterAll/afterEach

?

Hmm

Could you try

await worker.waitUntilExit()

instead?

running https://github.com/demosjarco/local-ip-geo/actions/runs/4387713341/jobs/7683334581

Are you sure instead? Or how else will it know when to stop?

I've been using it in my tests, and the entire suite takes ~5s

My test itself takes

duration_ms: 2049.776648

but the worker doesn't stop so the test script runs for infinity.