You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's nothing to stop an external package from implementing a custom renderer that follows the Svelte component spec (such as it is) – in fact I'm currently in the process of creating svelte-ssr which is basically exactly that. The question is the extent to which the core compiler is extensible enough to allow custom renderers to do their thing without reimplementing a lot of the tricky stuff.
With svelte-ssr I'm finding that it's just different enough that it deserves to be completely separate from the main compiler. I don't know how far that applies to those other examples. There are also cases where you might just want to hook into the compiler to add first class support for Redux/MobX/GraphQL/whatever.
For now I think it's early enough that we're better off thinking of those things as separate packages and learning which bits make sense to be plugins/hooks/whatever, and which truly belong in core.
Oh definitely I think that these things should be separate packages. I should have been more clear, I was referring to the core compiler being extensible enough (without requiring copying large amounts of code) to allow custom renderers (which I don't think it currently is).
Currently there's no way to use a custom renderer (see react renders for rendering to canvas, native, terminal, etc.)
The text was updated successfully, but these errors were encountered: