Gsxui – Shadcn-style components for Go

 (ui.gsxhq.dev)

45 points | by jackielii 4 hours ago

4 comments

  • sosodev 1 hour ago
    GSX seems interesting but I don’t understand why it depends on the node ecosystem. I just want to use Go for everything.
    [-]
    • jackielii 2 minutes ago
      because Vite is great. Try the gsx init. You'll know why. The dev experience you'll want
  • nzoschke 1 hour ago
    How does this compare to templ and templui? I see from the docs that gsx is templ compatible.

    And why does this depend on node / npx? Something to do with the JSX syntax and parsing?

    I wish go std templates were more ergonomic for components.

    Past that I wish projects like templ or GSX have a simple go generate pipeline, and support html and text/markdown output including whitespace.

    Until then I have a Frankenstein of a bunch of templating.

    [-]
    • jackielii 1 minute ago
      It doesn't depend on node for runtime. Only for dev: the vite dev server, and js bundling, nothing else
  • gen3 1 hour ago
    Looks good. I normally package a webui up with vite and serve that but I'll keep this in mind
  • skontraandrija 37 minutes ago
    does it work with htmx?