Resource Route Single Fetch Updates

[brophdawg11]

When single fetch is enabled:

• Raw javascript objects returned from resource routes are automatically wrapped in json() and a deprecation warning is logged
• Resource routes will receive the response stub for consistency and it will be respected, but the preferred way to handle status/headers is via your returned Response

Closes #9314

[changeset-bot]

🦋 Changeset detected

Latest commit: 19a4b17

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/server-runtime	Patch
@remix-run/cloudflare	Patch
@remix-run/deno	Patch
@remix-run/dev	Patch
@remix-run/node	Patch
@remix-run/react	Patch
@remix-run/testing	Patch
@remix-run/cloudflare-pages	Patch
@remix-run/cloudflare-workers	Patch
@remix-run/architect	Patch
@remix-run/express	Patch
@remix-run/serve	Patch
create-remix	Patch
remix	Patch
@remix-run/css-bundle	Patch
@remix-run/eslint-config	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

[manzano78]

@brophdawg11, does it mean that we can’t benefit from turbo-stream Date/Set/Map/Promise types in a useFetcher which load()s a resource route?

[brophdawg11]

@manzano78 No - when a fetcher hits a resource route it will still make a /resource.data request and it'll go through the turbo-stream-enabled code path. If you were to CURL a resource route, you'd get this json() behavior

[manzano78]

@brophdawg11 yes I can reproduce the turbo-stream format but since json() applies a simple JSON.stringify(data), I still receive a string instead of a Date in my fetcher's data :-/

[brophdawg11]

I'm not sure what the issue is. Fetchers can load from resource routes returning raw objects and they will be streamed using turbo-stream, which means you will not lose Date instances: https://stackblitz.com/edit/remix-run-remix-beoo1t?file=app%2Froutes%2F_index.tsx

This PR does not change that behavior when accessed via a fetcher.

If you are still having issues, would you be able to please open a github issue with a minimal reproduction?

[haines]

This is a great improvement, thank you! I ran into this after I refactored our authenticate helper to take the response stub to append the Set-Cookie header, so it's really nice to be able to use that from resource routes as well.

[ngbrown]

There is an errant å in the changset text.