I have tried, but still not find out a way to handle client side select without custom client Javascript.
Do you have any idea?
bluzky
0
olivermt
bluzky
bluzky
Update May 31
Added new component: Breadcrumb and Pagination
Check them here:
https://salad-storybook.fly.dev/salad_ui_component/breadcrumb
4
dennyabrain
Really appreciate the work on this. Been looking for feature rich component libraries to incorporate in my toolkit as well. Bookmarking this for later 
2
bluzky
03juan
You really shouldn’t try to avoid it, it’s there for a reason and I think it would be the perfect addition to this project. I’d recommend having a look at whatb melt-ui does for svelte components.
I wonder if that library could be used as a dev dependency, compiled and integrated into hooks akin to LiveSvelte, like a light-weight version of what shadcn-svelte does… 
I’d like to help explore this when I have some spare cycles, if you don’t get to it first
5
lawik
Nerves Core Team
I would definitely agree that shipping some hooks for necessary interactivity is reasonable. Good impulse to first try getting on without, but some components are likely trivial with a hook but convoluted or impossible without it.
I haven’t tried shipping a component with an integrated hook for others to use. I suppose you need to decide if that JS is a per-component import for app.js or figure out something smoother?
2
03juan
There are ways to load them dynamically as needed while hinting to the browser to prefetch and cache for performance gains. Basically a combination of promise-based import() and <script type="importmap"></script>
I’ll see about creating a PoC soon.
Anything ARIA-related is a prime candidate. Liveview has an implementation of this for wrapping tab focus on things like dropdown menus
1
cschmatzler
For what I’m building right now I’m essentially offering multiple options:
Ship the JavaScript with the hex dependency, which gets picked up automatically IF the default esbuild setup is used. Then either import the hook per component (e.g. import { Menu } from “…”) which minimises bundle size slightly OR have a convenience Hooks import that can be added as { …Hooks } which adds everything in one go but does include components you’re not using.
Or the same but published to npm for integration with more complex asset pipelines.
2