Karim Jordan

I think there is still an issue. According to [this Chrome article](https://developer.chrome.com/articles/css-nesting/#understanding-the-nesting-parser) the following should work but in Svelte it doesn't: ```html let name = 'world'; Hello {name}! .card {...

It doesn't work without an ampersand. I tried it in a [REPL](https://svelte.dev/repl/1af777763dad4afa9ea97169417ea1c0?version=3.59.1) and in SvelteKit. From what I understand the CSS parser that Svelte uses doesn't support optional ampersands and...

I found another potential issue. The following styles: ```html div { & :global(*) { color: yellow; } } div :global(*) { color: red; } ``` produce the following output: ```html...

Just to update, Vue handles this with the following option in its Vite plugin. Would be really great if we could do this in Svelte too: ```js plugins: [ vue({...

Is there a reproducible example of how this could currently create problems in SvelteKit and if not @illright could you create one?

Do you have a specific use case in mind?

Related issue: #4661

Any updates on this?

I just tried it out: ```bash ❯ node index.mjs "ssr" ssr [ '/docs/single-page-apps#prerendering-individual-pages', '/docs/types#public-types-server', '/docs/page-options#prerender-prerender-and-ssr', '/docs/routing#layout-layout-server-js', '/docs/page-options#csr', '/docs/routing#page-page-svelte', '/docs/types#public-types-ssrmanifest', '/docs/state-management#using-stores-with-context', '/docs/routing#layout-layout-js', '/docs/load#universal-vs-server-when-does-which-load-function-run' ] ``` In the current docs the first...

Other name suggestions were: - `fallback` - `other` - using the `default` export