WIP: Devinxi css rework

[katywings]

PR Checklist

Please check if your PR fulfills the following requirements:

• Addresses an existing open issue: fixes #000
• Tests for the changes have been added (for bug fixes / features)

Design Goals

1. Consistency between dev/prod
2. Prevent foucs
3. Avoid unused route css
4. Avoid duplicate css

Issues

• Create an example for css testing
• ?url imported css should not be server rendered
  • TODO: Needs a better way to detect ?url
• <link> should be mounted before suspension-end during spa navigation
• Suspension from spa navigation should only end after <link> has been loaded
• Assets should be deduplicated on ssr
• Integrate mountAssets in dev (making dev and prod use the same API)
• Public manifest and asset mount API (Edit: Public manifest API analog to RFC: Client assets metadata API for SSR vitejs/vite#20913 will be implemented in a different branch)

Known problems:

• 404 page is not server rendered
• app.css gets removed when navigating from /index to /about in css-garden
• <link> is mounted too early on spa navigation - it should wait until resources/createAsync is done

[changeset-bot]

⚠️ No Changeset found

Latest commit: 27fef42

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

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@solidjs/start@1965

commit: 27fef42

[brenelz]

This is still going to be post-devinxi into main?

[brenelz]

bunch of conflicts now too

[katywings]

This is still going to be post-devinxi into main?

@brenelz It's still up for discussion of this is going straight into devinxi or if it is going into main. Why 😅?

[katywings]

bunch of conflicts now too

@brenelz Just rebased it, conflicts are gone 😃. Next on my TODO list: rework the DEV part (try to render <link> in dev, instead of <style>).