panel
router
panel | router | |
---|---|---|
1 | 2 | |
272 | 402 | |
0.4% | 0.5% | |
5.7 | 4.0 | |
3 months ago | 5 months ago | |
JavaScript | HTML | |
- | Apache License 2.0 |
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.
panel
-
Web Components Will Outlive Your JavaScript Framework
Webcomponents will outlive React 13, mostly likely. Will they outlive React entirely or its cousins like Solid and Svelte? Perhaps not.
Webcomponents and React look like they solve the same problem but they do not.
Webcomponent api is pretty shallow. You get connected/disconnnected/attributeChanged call back but gotta write your own property setter and getters, and that’s mostly it. Shadow dom becomes a pain to work with if something needs to pierce it. Can’t pass nested objects in attributes, gotta encode as string.
Mixpanel went all in on webcomponents, but had to build a whole bunch of lib tooling around it. They made their own framework on top of webcomponents. https://github.com/mixpanel/panel
Worked on panel lib and webcomponent UI for many years. It is not a silver bullet.
The issue with webcomponents is there are a ton of libraries that fill in the missing gaps. There’s not a lot you can do with pure vanilla webcomponent api since browsers don’t provide efficient dom updating mechanism. Google has their own thing, Microsoft had multiple internal libs across orgs, Reddit does their own thing.
The most standard thing for frontend with wide adoption right now is React.
So the way I see it, is that React has already outlived webcomponents.
router
-
Router, pages, layouts and async data in TiniJS apps
Tini Router is the default way to add routing capability to TiniJS apps. There are also other routers you may use with TiniJS, such as: Vaadin Router and Lit Router.
-
Web Components Will Outlive Your JavaScript Framework
One approach I don’t mind is to just make a HTML file per screen in the application and route like the rest of the web.
When you bring in modern things like service workers and the prefetch API you can still very much keep the speed that is traditionally associated with SPAs.
Otherwise I’ve seen good things said about both of these options:
1. https://github.com/vaadin/router
What are some alternatives?
lit-state - Simple shared component state management for LitElement.
lit - Lit is a simple library for building fast, lightweight web components.
nonio-frontend
web-components-examples - A series of web components examples, related to the MDN web components documentation at https://developer.mozilla.org/en-US/docs/Web/Web_Components.
joystick - A full-stack JavaScript framework for building stable, easy-to-maintain apps and websites.
uibuilder - Typed HTML templates using TypeScript's TSX files
flyctl - Command line tools for fly.io services
live_state - The hex package for the server side of live state
h-include - Declarative client-side inclusion for the Web, using Custom Elements V1