Stephane

You are right this is not a bug as `name` never changes, you can also add a `$: console.log(name)` in the script to make it even more obvious (it will...

> IMO this is going in the right direction. Obviously we will never have the flexibility of JSX or HS with a SFC format, and that's totally fine. Logic-less pieces...

A top level category would disrupt the 'balance' it has now `A B C Logo D E F` which feels nice, if we add the sirens there as well one...

In regards to the comments in #20 where I mention making helpers that provide extra functionality to the components without necessary having to 'embed' that functionality in the component itself...

I did not make a list (yet) any input is welcome on that issue.

The carousel autoplayer could be envisioned like this ```html let carousel $: autoPlayer = carousel && new AutoPlayer(carousel) ``` with the AutoPlayer returning an interface allowing to play, pause, stop...

I feel like some extra background can be beneficial. I am trying to solve the 'translated routes' problem and came to this solution: route: `/routes/[about=about]/+page.svelte` and in `/matchers/about.js` ```js import...

> As in #4539, matchers in `+page.js` or `+page.server.js` is a no-go. Yes, I forgot about that one again, thanks for not reflexively closing this issue. > but it's still...

> What about `+match.name.ts` (or ,`+matcher.name.ts`) where `name` is the name of the param? It would allow multiple matchers and drop the awkward [name=matcher_type] syntax. Alternatively: allow one +matchers.ts with...

> He is talking about `routes/[param1=matcher1]-[param2=matcher2].[param3=matcher3]/+page.svelte`. > > Tho that could be resolved with: > > ```js > // routes/[param1=matcher1]-[param2=matcher2].[param3=matcher3]/+matcher.js > > export const param1 = ...; > export const...