chore(open-next): avoid the use of DurableObjects by using queueCache with memoryQueue instead

[dario-piotrowicz]

Description

The use of DurableObjects breaks the open-next skew protection, so in order to make sure skew protection works this PR updates the queue to use queueCache with memoryQueue instead of durable objects

Validation

Site built and deployed to my personal account: https://8bf0874a-nodejs-website-1.dario-test.workers.dev

Related Issues

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run pnpm format to ensure the code follows the style guide.
• I have run pnpm test to check if all tests are passing.
• I have run pnpm build to check if the website builds without errors.
• I've covered new added functionality with unit tests if necessary.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nodejs-org	Ready	Preview	May 5, 2026 11:41pm

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.23%. Comparing base (ae82cde) to head (75115e7).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8878      +/-   ##
==========================================
+ Coverage   73.18%   73.23%   +0.04%     
==========================================
  Files         102      102              
  Lines        8623     8623              
  Branches      314      313       -1     
==========================================
+ Hits         6311     6315       +4     
+ Misses       2311     2307       -4     
  Partials        1        1              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[vicb]

LGTM (I can not approve here it seems).

Do we need to add a delete migration for former DOs?

[dario-piotrowicz]

LGTM (I can not approve here it seems).

Thanks 🙂

Do we need to add a delete migration for former DOs?

I think a delete migration is used when a class is deleted but the durable object binding is still used.
Since here we are instead completely removing the durable object I think that the simplest / most appropriate way to delete it is doing so though the dashboard. Don't you think?

[vicb]

the simplest / most appropriate way to delete it is doing so though the dashboard

+1