view_component
Our great sponsors
| view_component | services-as-dom-elements | |
|---|---|---|
| 74 | 2 | |
| 3,148 | - | |
| 1.3% | - | |
| 9.0 | - | |
| about 6 hours ago | - | |
| Ruby | ||
| 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.
services-as-dom-elements
-
We Use Web Components at GitHub
Would love to see why they did not choose lit-element, it was one of the best I tried in a recent experiment of ~5 solutions.
The big thing holding back webcompinents at this point is a data sharing strategy, and I think we could get away with actually using components to store and manage data:
https://www.vadosware.io/post/sade-pattern-services-as-dom-e...
The github repo (which also happens to contain how to write a web component in lit-element, slim.js, tonic, vue, svelte):
https://gitlab.com/mrman/services-as-dom-elements
What are some alternatives?
Stimulus - A modest JavaScript framework for the HTML you already have
ficusjs - FicusJS is a set of lightweight functions for developing applications using web components
turbo-rails - Use Turbo in your Ruby on Rails app
soci-frontend - [Moved to: https://github.com/jjcm/nonio-frontend]
Tailwind CSS - A utility-first CSS framework for rapid UI development.
cypress-rails - Helps you write Cypress tests of your Rails app
web3-sign-msg - web3-sign-msg is a modern web component built with ficusjs to sign messages with your eth private key in Metamask
hotwire-rails - Use Hotwire in your Ruby on Rails app
community-protocols - Cross-component coordination protocols
i18n-tasks - Manage translation and localization with static analysis, for Ruby i18n
open-wc - Open Web Components: guides, tools and libraries for developing web components.