Replies: 1 comment
-
|
Personally, I think this should be done in user land, see e.g. https://runed.dev/ |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
One thing I really love about Svelte is how much it gives you natively, without needing to rely on third-party libraries for basic frontend UI patterns.
However, I keep seeing the same few pieces of functionality repeated again and again, not only in my own codebases, but also across tutorials, examples, and real-world apps:
Yes, all of these can be implemented manually, and the implementations are usually not too difficult. But because these patterns show up so often, I think having more native support for them in Svelte would be incredibly useful.
These are the kinds of small-but-important primitives that make building great frontend applications smoother, more consistent, and less repetitive.
Curious what others think: would it make sense for Svelte to provide native primitives for these patterns?
Beta Was this translation helpful? Give feedback.
All reactions