vite: cloudflare preset load context

[pcattori]

Closes: #

• Docs
• Tests

Testing Strategy:

[changeset-bot]

🦋 Changeset detected

Latest commit: 1917bc3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 16 packages

Name	Type
@remix-run/dev	Patch
create-remix	Patch
remix	Patch
@remix-run/architect	Patch
@remix-run/cloudflare	Patch
@remix-run/cloudflare-pages	Patch
@remix-run/cloudflare-workers	Patch
@remix-run/css-bundle	Patch
@remix-run/deno	Patch
@remix-run/eslint-config	Patch
@remix-run/express	Patch
@remix-run/node	Patch
@remix-run/react	Patch
@remix-run/serve	Patch
@remix-run/server-runtime	Patch
@remix-run/testing	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

🤖 Hello there,

We just published version 2.6.0-pre.1 which includes this pull request. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!

[github-actions]

🤖 Hello there,

We just published version 2.6.0-pre.2 which includes this pull request. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!

[kiliman]

@pcattori Is setRemixDevLoadContext considered a public API?

I'm using a custom Express server, so it would be nice if I could set the load context in the Vite dev server as well.

[pcattori]

@kiliman : no, its not considerd public API.

The idea is that for Node-based custom servers, you can use the same server for both dev and prod where you can choose to delegate asset handling and route handling to Vite in dev. In that world, you already have direct access to createRequestHandler where you can do whatever you'd like with loadContext. And the best part is that your load context is automatically consistent in dev and prod.

The issue with CF is that (as of today) Vite can't delegate server code execution to other runtimes (like workerd) so you can't run the same server for dev and prod (yet). So setRemixDevLoadContext is a temporary stopgap for CF to approach parity with Node-based custom servers.

[kiliman]

True. Thanks!

[github-actions]

🤖 Hello there,

We just published version 2.6.0 which includes this pull request. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!