web-components-examples
router
web-components-examples | router | |
---|---|---|
3 | 2 | |
2,989 | 405 | |
1.4% | 1.5% | |
4.2 | 4.0 | |
21 days ago | 6 months ago | |
JavaScript | HTML | |
Creative Commons Zero v1.0 Universal | 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.
web-components-examples
-
Web Components Will Outlive Your JavaScript Framework
I was excited for web components, but the API was lacking (the final tipping point that led me to build Joystick [1]). I just couldn't get on board with a web-standard that eschewed HTML in favor of stuff like this [2] where list items are attributes. The hyphenated namespace thing has always made my eye twitch, too (silly, I know).
[1] https://github.com/cheatcode/joystick
[2] https://github.com/mdn/web-components-examples/blob/main/edi...
-
How is Web Components used with React?
I just found out about Web Components and read that they can be used complementary with React. This concept of Web Components are new to me as I thought only library/frameworks were used to create re-usable component. I'm just wondering how are Web Components used in modern frontend development and if there are any examples that I can refer to such as github or codepen where Web Components are used within React. So far I found this example from MDN: https://github.com/mdn/web-components-examples
-
can i share web components across pages?
Second, you’ll just import the JavaScript file where you’ve defined your web components into each html file. Example.
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?
nonio-frontend
lit - Lit is a simple library for building fast, lightweight web components.
panel - Web Components + Virtual DOM: web standards for powerful UIs
flyctl - Command line tools for fly.io services
lit-state - Simple shared component state management for LitElement.
live_state - The hex package for the server side of live state
joystick - A full-stack JavaScript framework for building stable, easy-to-maintain apps and websites.