Justinas Delinda

Experiencing the same issue though not using nuxt and just global `declare` for some internal package in my monorepo. Last working version for my was `vue-tsc` `2.0.22`. 24 starts failing...

I patched it for myself quick replace `,)` -> `, )`, but another issue seems missing space between variable and shadow numbers, which prevents it working.

That spec change is relatively recent, if I am not mistaken Chrome shipped it this year, so lightingcss should not remove spaces there especially when target is bit older browsers.

I might have confused whitespace trimming with Browsers allowing [invalid fallback to work](https://groups.google.com/a/chromium.org/g/blink-dev/c/yc4XmGZi1Mk/m/1LNETNyzAwAJ) which did ship this year. Though lightingcss still should not remove those spaces when browser target is...

I might be wrong, but think I am experiencing this while having structure like `(dash)/(home)`. ``` router.ts:21 [Vue Router warn]: The route named "/(dash)" has a child without a name...

Yeah, but more specifically in Sveltekit it is the only way to define page, each route must be their own folder and contain +page. There is no ambiguity between `user/+page.svelte`...