chore(rsc): update vite-rsc for automatic server css support

[hi-ogawa]

Hey, I'm iterating server css support and this is just one attempt to make it easier for certain routing system. I'm sharing it here in case you are interested. Here is an updated API https://github.com/hi-ogawa/vite-plugins/tree/main/packages/rsc#idvite-rsc-css-exportname. Please feel free to take or close it.

---

Putting it to draft as I'm thinking more automatic approach.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c03f1a6

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

[Hardanish-Singh]

LGTM!

[brookslybrand]

Hey @Hardanish-Singh I appreciate you trying to be helpful, but approvals and comments like these aren't helpful, they just add noise. I've seen you jump on a number of PRs with what are essentially auto approvals. If I keep seeing it I'm going to have to block you

Please refrain from reviewing PRs in the future unless you are actually giving feedback on the code

[markdalgleish]

@hi-ogawa What about routes with multiple component exports? Will the API support this?

Also, have you see the way Parcel handles this? https://github.com/parcel-bundler/parcel/blob/d948759d2fd502bc0c76cf87480f6fb12d2a2ee6/packages/runtimes/rsc/rsc-helpers.jsx#L22-L90 — it's a bit wild, but I like that consumers don't need to think about it.

[hi-ogawa]

Yes, I've seen Parcel's idea and I'm experimenting with something similar too. I actually just landed this one hi-ogawa/vite-plugins#1030, so I'll update the example here.