fix(remix): Fix issue where request body has already been read

[octoper]

Description

This PR fixes a bug where the body has already been read and we try to clone the whole request and this results to an error.

Fixes #3769

Checklist

• npm test runs as expected.
• npm run build runs as expected.
• (If applicable) JSDoc comments have been added or updated for any package exports
• (If applicable) Documentation has been updated

Type of change

• 🐛 Bug fix
• 🌟 New feature
• 🔨 Breaking change
• 📖 Refactoring / dependency upgrade / documentation
• other:

[changeset-bot]

🦋 Changeset detected

Latest commit: 3aaf608

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

This PR includes changesets to release 1 package

Name	Type
@clerk/remix	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

[octoper]

!snapshot

[clerk-cookie]

Hey @octoper - the snapshot version command generated the following package versions:

Package	Version
@clerk/astro	1.0.5-snapshot.vb3a15ea
@clerk/backend	1.5.0-snapshot.vb3a15ea
@clerk/chrome-extension	1.1.8-snapshot.vb3a15ea
@clerk/clerk-js	5.10.3-snapshot.vb3a15ea
@clerk/elements	0.10.8-snapshot.vb3a15ea
@clerk/clerk-expo	2.0.1-snapshot.vb3a15ea
@clerk/express	0.0.22-snapshot.vb3a15ea
@clerk/fastify	1.0.24-snapshot.vb3a15ea
gatsby-plugin-clerk	5.0.0-beta.45
@clerk/localizations	2.5.3-snapshot.vb3a15ea
@clerk/nextjs	5.2.9-snapshot.vb3a15ea
@clerk/remix	4.2.8-snapshot.vb3a15ea
@clerk/clerk-sdk-node	5.0.21-snapshot.vb3a15ea
@clerk/tanstack-start	0.1.12-snapshot.vb3a15ea
@clerk/testing	1.2.4-snapshot.vb3a15ea

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/astro

npm i @clerk/astro@1.0.5-snapshot.vb3a15ea --save-exact

@clerk/backend

npm i @clerk/backend@1.5.0-snapshot.vb3a15ea --save-exact

@clerk/chrome-extension

npm i @clerk/chrome-extension@1.1.8-snapshot.vb3a15ea --save-exact

@clerk/clerk-js

npm i @clerk/clerk-js@5.10.3-snapshot.vb3a15ea --save-exact

@clerk/elements

npm i @clerk/elements@0.10.8-snapshot.vb3a15ea --save-exact

@clerk/clerk-expo

npm i @clerk/clerk-expo@2.0.1-snapshot.vb3a15ea --save-exact

@clerk/express

npm i @clerk/express@0.0.22-snapshot.vb3a15ea --save-exact

@clerk/fastify

npm i @clerk/fastify@1.0.24-snapshot.vb3a15ea --save-exact

gatsby-plugin-clerk

npm i gatsby-plugin-clerk@5.0.0-beta.45 --save-exact

@clerk/localizations

npm i @clerk/localizations@2.5.3-snapshot.vb3a15ea --save-exact

@clerk/nextjs

npm i @clerk/nextjs@5.2.9-snapshot.vb3a15ea --save-exact

@clerk/remix

npm i @clerk/remix@4.2.8-snapshot.vb3a15ea --save-exact

@clerk/clerk-sdk-node

npm i @clerk/clerk-sdk-node@5.0.21-snapshot.vb3a15ea --save-exact

@clerk/tanstack-start

npm i @clerk/tanstack-start@0.1.12-snapshot.vb3a15ea --save-exact

@clerk/testing

npm i @clerk/testing@1.2.4-snapshot.vb3a15ea --save-exact

[wobsoriano]

This looks good to me. I initially wondered why cloning the request wasn't sufficient, but I realized that it's possible to read the request in userland before passing it to the getAuth helper