Thanks for the suggestion. I did look into this in the past, and don't feel comfortable opting into this, at least in its current form. The styles will always be different, the templates different, the callback arguments from events different leaving the only thing shared being the script tag. Svelte components tend to have a small script tag and most common logic is extracted into stores, or plain JS.

I feel that forcing a 1 for 1 component mapping between native and web could lead to compromises in application layout/design.

That being said, Svelte does has a pre-processor option which could be used to do this and remove the style and unwanted template based on target, so I will leave this to a preprocessor and not bake it into core.

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions