view_component
storybook
Our great sponsors
view_component | storybook | |
---|---|---|
74 | 321 | |
3,148 | 82,727 | |
1.3% | 0.7% | |
9.0 | 10.0 | |
about 12 hours ago | 7 days ago | |
Ruby | TypeScript | |
MIT License | 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.
view_component
- Things I wish I knew before moving 50K lines of code to React Server Components
-
Supercharged table component built with ViewComponent
When searching for examples of table components built with the ViewComponent gem, I was surprised to find none. After some inquiries, I came across examples that worked like this:
-
More expressive APIs for View Components
View components offer two primary ways to interact with the component: passing arguments to the initializer and using slots:
- Have you been using ViewComponent. What advantages do you see in it?
-
How can I integrate VueJS into a rails 7 application? What is the workflow?
For example, splitting out views into partials? Or the new ViewComponent feature that's becoming quite popular - https://viewcomponent.org/
- Helpers vs Components
-
Vanilla Rails view components with partials | Stanko K.R.
I used to do "pure ruby" approach to that -- but basically wound up realizing I was re-inventing github's view_component. Their design goals were similar enough to what I was trying to do, that it made more sense just to use that, rather than try to re-invent it myself.
-
Gnarly Learnings from March 2023
ViewComponent
- Os benefícios de componentizar as views do Rails
-
Does anyone kind of miss simpler webpages?
The linked one is my Rails implementation, written for ViewComponent. The official version uses Nunjucks.
storybook
-
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!)
-
Storybook 7.6 is out!
[Storybook 7.6](https://github.com/storybookjs/storybook/releases) is here with increased performance and much more! 🔥 Improved SWC support 🧪 New test utilities and fast build mode 🔼 NextJS SWC + avif support & fixes 🤡 SvelteKit page and navigation mocking ⚛️ React-docgen upgrade 🎨 Controls a11y, background theming, and viewports 🩺 CLI: The doctor is in! 🚫 Addons: Remove React as a peer dependency 🪦 Storyshots and Vue2 deprecated
What are some alternatives?
Stimulus - A modest JavaScript framework for the HTML you already have
Docusaurus - Easy to maintain open source documentation websites.
turbo-rails - Use Turbo in your Ruby on Rails app
fluentui-blazor - Microsoft Fluent UI Blazor components library. For use with .NET 6.0 or higher Blazor applications
Tailwind CSS - A utility-first CSS framework for rapid UI development.
react-styleguidist - Isolated React component development environment with a living style guide
cypress-rails - Helps you write Cypress tests of your Rails app
fractal - A tool to help you build and document website component libraries and design systems.
hotwire-rails - Use Hotwire in your Ruby on Rails app
svelte-luna - svelte ui kit
i18n-tasks - Manage translation and localization with static analysis, for Ruby i18n
primeng - The Most Complete Angular UI Component Library