Make site work with the Cloudflare OpenNext adapter

[dario-piotrowicz]

This PR applies changes to make it so that the site can be deployed to Cloudflare workers using the open-next Cloudflare adapter

The app does seem to work as intended for the most part:

Deployment URL: https://nodejs-website.web-experiments.workers.dev

---

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run npm run format to ensure the code follows the style guide.
• I have run npm run test to check if all tests are passing.
• I have run npx turbo 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 Git ↗︎

Name	Status	Preview	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	May 8, 2025 11:14pm

[ovflowd]

@dario-piotrowicz do we have updates here? 👀

[dario-piotrowicz]

Hey @ovflowd 👋

Sorry for keeping the PR lingering, there are a few smaller issues we addressed in our adapter (that I need to reflect here), and also ISR should be coming soon (@vicb can provide more context)

Besides that I just need to rebase the PR, the only significant issue remaining should be filesystem access, but I wanted to clarify that with you, I'll drop you a message today to clarify things

(PS: I hope the PR is not bothering you 🙇, if you want I can close it and reopen it when we're ready?)

[ovflowd]

Sorry for keeping the PR lingering, there are a few smaller issues we addressed in our adapter (that I need to reflect here), and also ISR should be coming soon (@vicb can provide more context)

This is awesome news. Excited to hear from @vicb

Besides that I just need to rebase the PR, the only significant issue remaining should be filesystem access, but I wanted to clarify that with you, I'll drop you a message today to clarify things

I believe we sorted that out on Slack 🖖

(PS: I hope the PR is not bothering you 🙇, if you want I can close it and reopen it when we're ready?)

Not at all <3

[avivkeller]

Once the reviews are resolved, LGTM

[avivkeller]

Once #7383 (comment) #7383 (comment) resolve, this can probably land 🎉

[avivkeller]

However, I would love if there was a test in the CI to verify this builds for any given push/PR.

[dario-piotrowicz]

However, I would love if there was a test in the CI to verify this builds for any given push/PR.

mh... that's an interesting idea.... we've considered PR previews + e2es but not something that purely tests the build aspect of this 🤔

I wouldn't be against it, I am not sure how much extra confidence that would give us, but it'd definitely not hurt either (besides the potential extra noise etc...)

I'm totally happy to look into that 🙂
I think I'd prefer to do that as a followup PR and finally land this one, but I can also include it here if you prefer 🙂

[avivkeller]

It can totally be a follow up, I just don't want us to have the unfortunate scenario where PR deploys successfully on Vercel, but not on OpenNext.

[ovflowd]

LGTM after my final comments get addressed

[dario-piotrowicz]

LGTM after my final comments get addressed

Thanks Claudio 😃

There's still #7383 (comment) outstanding, please give it a quick look (it should be rather minor in any case)

[avivkeller]

Did you link the right discussion? That one’s resolved with the conclusion that no changes are needed.

[dario-piotrowicz]

Did you link the right discussion? That one’s resolved with the conclusion that no changes are needed.

Nope, sorry I pointed to the wrong one, thanks for spotting it, I've updated the link 🙂👍