helix
storybook
helix | storybook | |
---|---|---|
16 | 322 | |
608 | 82,881 | |
- | 0.5% | |
5.6 | 10.0 | |
18 days ago | 1 day ago | |
Clojure | TypeScript | |
Eclipse Public License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
helix
-
create-helix-app: project templates with Helix and more
In short, performance, easier interop with JS react libraries, better static analysis, and being able to use modern React features. For more details, see https://github.com/lilactown/helix/blob/master/docs/motivation.md and https://github.com/lilactown/helix/blob/master/docs/faq.md#what-about-hiccup. It's also worth checking this blog post: https://fbeyer.com/posts/refx-origins/
-
Is there a simply way to write small, portable UIs in Clojure/script? Something akin to Elm
You can ignore the malli/react-hook-form part - the relevant parts are the entry namespace and the shadow-cljs config. This example uses https://github.com/lilactown/helix (great tutorial here https://github.com/iwrotesomecode/react-docs-helix) but you can use reagent if you wish. I think this should meet your requirements. You can inline your data in the cljs bundle as data and add UI via react components.
-
React.dev - are CLJS developers using Reagent in trouble?
[1] https://github.com/lilactown/helix [2] https://github.com/ferdinand-beyer/refx
-
React.dev
> But Reagent supports functional components as well, with hooks and all.
I addressed this already: while reagent is able to emit function components, there is a performance penalty to this.[1]
> I also very much like Hiccup, and so do many of us, because code is data and data is code, and Helix has decided not to support that.
Hiccup is convenient to write, but it is a constant run-time cost and a significant storage cost given that you have to store long series of constructors to cljs.core.PersistentVector in your bundle, have the JS runtime actually construct the vector, then pass it through a Hiccup interpreter to finally produce DOM nodes and throw away the persistent vector, only to repeat this entire process again on re-render.[2]
> Helix has decided not to support that.
That is simply not true. From the Helix documentation[2],
> If you want to use libraries like sablono, hicada or even hx hiccup parser, you can easily add that by creating a custom macro.
These are all Hiccup interpreters you can readily use.
IME there is very little difference between using the $ macro in Helix and writing Hiccup. I do not really miss Hiccup when I use Helix, and you still have data as code ;)
While this is from an unrelated project, there are benchmarks[3] done against Reagent that demonstrate the sheer overhead it has. In practice it is not a big problem if you rarely trigger a re-render, but otherwise it is a non-trivial cost, and if you want to use modern React features (like Suspense), there is a lot of r/as-element mingling going on, converting cases, etc. that simply make Reagent feel more tedious to use than Helix.
Also, the newer UIx2, which largely borrows from Helix, is "3.2x faster than Reagent" according to one of the contributors.[4]
I think it'd be worthwhile to benchmark all of these libraries against each other and record the data in one place. Maybe I'll get around to doing it this weekend :)
---
[1] https://github.com/reagent-project/reagent/blob/master/doc/R...
[2] https://github.com/lilactown/helix/blob/master/docs/faq.md#w...
[3] https://github.com/roman01la/uix#benchmarks
[4] https://github.com/pitch-io/uix/pull/12
-
What is the state of frontend animation in React/ClojureScript?
Helix is also worth checking our for lightweight React integration and hooks support.
- reframe or plain reagent for new cljs SPA?
-
How does Reagent/re-frame bypass the prolifeation of React hooks?
Helix is a thinner library with access to hooks, if you want them.
-
Reflecting on 18 months of Clojure - Building a SaaS business with Clojure
helix
-
re-frame vs react
You mentioned liking React hooks, would helix be more to your liking?
-
Keechma vs Keechma.next
Keechma/next is integrated directly with React through the hooks system (and using the excellent Helix library. You can find the integration code in the Keechma/next toolbox - especially https://github.com/keechma/keechma-next-toolbox/blob/master/src/keechma/next/helix/core.cljs
storybook
-
How to use NextJS pathname in Storybook 8
Source: qcatch on Feb 22, 2024 https://github.com/storybookjs/storybook/discussions/25470
-
Storybook not picking up tailwindcss
[Bug]: Configuration with TailwindCss Next.js using Tailwind with Storybook
-
Astro.js as an alternative to Next.js: pushing the limits
Astro has no runtime. This means no unit tests. This also means no Storybook for your Astro components (although, they’re working on it!)
-
Release Radar • March 2024 Edition
If you're into UI development, then you need to know about Storybook. It's a frontend workshop for building UI components and pages in isolation. The latest version brings some big improvements for testing and documentation with built-in visual testing. There's also React Server Component support, improved controls for React and Vue projects, as well as improved Vite architecture, Vitest testing, and Vite 5 support. Check out all the major changes in the Storybook changelog.
-
Top 10 Tools Every React Developer Needs in 2024
Storybook
-
Announcing AnalogJS 1.0 🚀
We are continuing to make building fullstack websites and application with Analog and Angular as seamless as possible, and extending the Angular ecosystem through integrations with Astro, Nx, [Vitest]https://analogjs.org/docs/features/testing/vitest, Storybook, and more.
-
Storybook 8
Storybook is the industry standard UI tool for building, testing, and documenting components and pages. It’s used by thousands of teams globally, integrates with all major JavaScript frameworks, and combines with most leading design and developer tools.
-
Add Cypress, Playwright, and Storybook to Nx Expo Apps
Expo has first-class support for building full-stack websites with React, so I can leverage that to add Cypress/Playwright for E2E testing and add the Storybook for UI components.
-
13 best React debugging tools
Storybook emerges as a pioneering solution among React debugging tools, offering an interactive environment for developers to create and test UI components. With its robust platform, teams can build, organize, and design UI components, and even entire screens, without the hurdles of business logic and plumbing.
-
Javascript is hard ayy eff
3) Look into things like StoryBook for your components - https://storybook.js.org/ - they help you get into good practices and expose you to some more advanced techniques but in a gradual and friendly way, and again, it's good to get into good habits from the start, and these help make sure you're getting into those good habits (it can be hard to learn good habits, but being forced into them helps, I find!)
What are some alternatives?
uix - Idiomatic ClojureScript interface to modern React.js
Docusaurus - Easy to maintain open source documentation websites.
reagent - A minimalistic ClojureScript interface to React.js
fluentui-blazor - Microsoft Fluent UI Blazor components library. For use with ASP.NET Core Blazor applications
shadow-cljs - ClojureScript compilation made easy
react-styleguidist - Isolated React component development environment with a living style guide
liveview-clj
fractal - A tool to help you build and document website component libraries and design systems.
om - ClojureScript interface to Facebook's React
svelte-luna - svelte ui kit
storybook.js-with-shadow-cljs
primeng - The Most Complete Angular UI Component Library