Event Driven Architecture Vanilla JS Web Components codebase containing real world examples (CRUD, auth, advanced patterns, etc) that adheres to the RealWorld spec and API.
This codebase was created to demonstrate a fully fledged fullstack application built with Event Driven Vanilla JS Web Components including CRUD operations, authentication, routing, pagination, and more.
We've gone to great lengths to adhere to the Document Object Model (DOM) community styleguides & best practices.
For more information on how to this works with other frontends/backends, head over to the RealWorld repo.
Frontend Event Driven Architecture works basically like the DOM itself. There are loosely coupled components (nodes), which emmit events and those get captured by controllers also called stores, routers, etc. Those controllers emmit events on their behalf, which the components can consume.
Simply open the src/index.html on a local or remote web server like, node live-server, apache, nginx, xampp, etc. Tests: Open the test/index.html
Here you can find the 👉 event driven web components tutorial
-
ShadowDOM's mostly shine when encapsulating CSS. But the Conduit example has one global CSS Stylesheet and for that reason, it is more efficient not to have shadowDOM's, which all would have to import that global CSS separately. Note: The biggest strength of Web Components is their shadowDOM, means in a real life examples you would share general CSS styles through CSS variables and have specific styles on each component in their respective shadowDOM. This will improve performance, since the DOM renderer only needs to respect certain CSS for certain nodes/shadowDOM's. There is a good helper Class, which you can use to simply add CSS with the lines:
this.css = '...'and for avoiding to reset nodes with innerHTML, it includes functions like:this.html = ''. Overall, this prototype Class helps you to easily and comfortably deal with the ShadowDOM. Have a look at: Shadow.js -
Dependencie's: This application uses ZERO production dependencies. One devDependency is used for linting, see the package.json for further details.
-
Size: 35 items, totalling 143.1 kB uncompressed
- TailorMadeCode Components Development
- V4L3 Components Development
- Weedshaker Architecture, Tests & Components Development
- rehrbar who was an essential part of developing the first PoC of an Event Driven Architecture, helping me to challenge ideas and concepts to its perfection with his profound software engineering background.