do not resolve renderer.serverEntrypoint url before loading it

[FredKSchott]

Changes

• Followup to fix windows package export #4141 to attempt a fix for one of the two Windows issues: renderer. serverEntrypoint
• Vite 3 appears to not like having resolved package exports passed to ssrLoadModule (but only on Windows?) and instead expects the unresolved package entrypoint.
• This is only safe to remove if we can confirm that the bug that this comment is referencing is out of date. I've confirmed that this change runs fine in the examples, but unclear which exact issue it was addressing since this is only ever used for loading renderers. @bholmesdev maybe you remember?

Testing

• Unclear if this is covered by existing tests or not. @bholmesdev to confirm?

Docs

• N/A

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7c615ea

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

[matthewp]

The commit where this was previously changed is here: 098f6f6

That commit was a workaround for an underlying Vite bug that resurfaced and was ultimately fixed here: vitejs/vite#8533. So I think we can merge this change.

[bholmesdev]

That bug @matthewp linked looks familiar to me! I agree this should be fixed with the new isSelfAccepting behavior. Pretty comfortable merging with these passing tests 👍