fix(nuxt): lazy-load entry CSS

[danielroe]

🔗 Linked issue

resolves nuxt/nuxt#14953

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

With nuxt-contrib/vue-bundle-renderer#39, we are now not blocking render with stylesheet, but we still need to load entry CSS on client side to include client-only CSS (among other things). This PR:

1. adds back support for rendering inline styles for ssr: false routes: fix(nuxt): don't inline styles for per-request ssr: false #8106
2. adds in lazy css links which use onload media strategy to load CSS on client-side only

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[codesandbox]

  Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

[netlify]

✅ Deploy Preview for nuxt3-docs canceled.

Name	Link
🔨 Latest commit	271f834
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/634e903135ca5400085ac1e1

[pi0]

Wouldn't they register as side-effects of #paths? (and if they do, do we still need it from #paths?

[danielroe]

They aren't registered as globals there.

And yes, we probably could wrap these lines in if (process.client) - will try:

framework/packages/nuxt/src/core/templates.ts

Lines 243 to 244 in c404cb1

	'globalThis.__buildAssetsURL = buildAssetsURL',
	'globalThis.__publicAssetsURL = publicAssetsURL'