Safeguard of H3Event body stream locking in edge runtime workaround

[supersoniko]

PR Checklist

Please check if your PR fulfills the following requirements:

• [ ] Tests for the changes have been added (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• [x] Bugfix
• [ ] Feature
• [ ] Code style update (formatting, local variables)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] CI related changes
• [ ] Documentation content changes
• [ ] infrastructure changes
• [ ] Other... Please describe:

What is the current behavior?

https://github.com/solidjs/solid-start/blob/main/packages/start/src/runtime/server-handler.ts#L136 There's currently a workaround for edge runtimes to create a new Request object instead of using the current one.

What is the new behavior?

Add a safeguard for the edge runtime workaround when a stream is already locked to not create the new Request object.

Other information

My goal is to make Solid Start work 100% on the Azure Functions runtime. I currently have a PR open at Nitro to support the latest Azure Function runtime.

However there's currently an issue that the H3 event body stream is already locked when it gets to the part of the edge runtime workaround when running on Azure Functions, which causes issues with server actions.

Im happy to say that all Solid Start functionality seems to work on Azure Functions once we get around this locking issue.

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 23324136d56ff4b42cacd81944948642bba916b4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[ryansolid]

Yeah I see hacks on hacks in there. I'm glad you figured something out. That being said. I'm going to probably need to test this fix against Vercel/Netlify edge as I thought the creation of the new Request was to get around stream locking so this fix may impact them.