component-party.dev
| component-party.dev | immaculatalibrary.com | |
|---|---|---|
| 3 | 5 | |
| 2,260 | 0 | |
| - | - | |
| 8.4 | 9.8 | |
| 4 days ago | 8 days ago | |
| JavaScript | TypeScript | |
| MIT License | GNU General Public License v3.0 or later |
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.
component-party.dev
immaculatalibrary.com
- Show HN: A new way to create universal/ssr TypeScript apps with JSX
-
Fairly sure I just made something better than React
Where is an example? https://github.com/sdegutis/immaculatalibrary.com/tree/main/... ?
-
Lit 3 Release Announcement
Overall I'm not super happy with web components to solve the issues of reusability, conciseness, and self-containment.
The most direct problem is styling issues. Cross-component CSS in either direction has some serious limitations. I've written a little bit about it[1] in my blog but the short version is that there are some things that simply become absolutely impossible when using web components.
My main other gripe with them is the need for a build phase. The nature of WC almost begs for them to eventually become zero-build-time, but right now this just isn't practical. It requires too much boilerplate in every .html file (utf8 is broken on my site), the syntax isn't natively there even with tagged template literals, and there's no concept of data-list-fetching or data-based file generation.
There's a branch on my personal website[2] where I tried to start using web components, and it was so problematic that I long abandoned it.
Overall, I abandoned web components entirely in favor of making my own customized JSX-based SSG from scratch[3] which solves the same problems Lit, Next.js, et al. are intended to solve, but in a completely different way: using components for convenience, conciseness, and reusability, but only at the build-phase time. So far it's a well kept secret, which is probably good since it's been evolving so quickly that I wouldn't have been happy with any iteration being widely adopted so far. (Though I think this morning I finished off most of what I was unhappy with.)
[1]: https://sdegutis.github.io/articles/2023-08-07-modern-90s-we...
[2]: https://github.com/sdegutis/immaculatalibrary.com/tree/reset...
[3]: https://github.com/sdegutis/immaculatalibrary.com
- Show HN: Fast Jekyll Alternative in TypeScript with JSX
What are some alternatives?
ardi - Ardi makes it easy to create reactive custom elements that work with any website or Javascript framework.
webcomponents - Web Components specifications
capacitor-solidjs-templates - Build native iOS, Android, and Web apps with Capacitor, SolidJS, and Vite
lit - Lit is a simple library for building fast, lightweight web components.
flapjax - functional reactive programming for JavaScript
shoelace-css - A collection of professionally designed, every day UI components built on Web standards. SHOELACE IS BECOMING WEB AWESOME 👇👇👇
esrap - Parse in reverse
lit - Fast server-rendering and client-hydration of lit-html templates and web components
sudoku-solver - Sudoku Solver
signals - Manage state with style in every framework
meteor-solid-app - Meteor.js with Vite, Solid, and Tailwind CSS