A personal note from EY:
This library is a cumulation of ~20 years of experience — from writing static HTML pages as someone who just needed a website, to building fully functional CMS systems when needed.
What I always needed was JavaScript. And for a while, jQuery did the trick, but I was looking for something that handled event delegation without me even knowing the concept — I simply knew what I needed: no add- & remove Listener chaos, just because i needed some interactive buttons or input elements.
jQuery couldn’t quite deliver that. Or rather, it technically could, but I couldn’t figure out how to do event delegation properly.
Then, over 10 years ago, I discovered the pretty unspectacular handleEvent interface. My entire JavaScript approach instinctively shifted towards event delegation (still without knowing its formal name).
The first thing I did on new projects since: I created a minimalistic version of what YEH does today — though not even close to what YEH can do now.
At the end, it does event delegation — a concept older than JavaScript itself, presumably even older than me.
BTW, now I know, and I admit it, in the first few years I didn’t even implement it properly because i didn’t knew how and there were no tutorials at all. Or maybe there were a few, but a few was as good as none back in the days. And with that out of the way:
Advanced web components with YEH (Yai Event Hub) - Enterprise-grade tabs with efficient event delegation
Build deeply nested, event-heavy interfaces with constant-time listener delegation and zero manual lifecycle handling. Everything you need in one package.
@yaijs/core packagefile://, CDN, or bundler with zero build required<!DOCTYPE html>
<html>
<head>
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@yaijs/core@latest/tabs/yai-tabs.css">
</head>
<body>
<div data-yai-tabs data-theme="default">
<nav data-controller>
<button data-tab-action="open" data-open="1">Tab 1</button>
<button data-tab-action="open" data-open="2">Tab 2</button>
</nav>
<div data-content>
<div data-tab="1">Content 1</div>
<div data-tab="2">Content 2</div>
</div>
</div>
<script type="module">
import { YaiTabs } from 'https://cdn.jsdelivr.net/npm/@yaijs/core@latest/dist/yai-bundle.js';
new YaiTabs();
</script>
</body>
</html>
npm install @yaijs/core
import { YaiTabs, YEH } from '@yaijs/core';
const tabs = new YaiTabs({
defaultBehavior: 'fade',
autoFocus: true
});
// Or extend YEH directly for custom event orchestration
class AppBus extends YEH {
constructor() {
super({ '#app': ['click', 'input', 'change'] });
}
}
.on().emit())| Complete YaiTabs Documentation → | Live Demo → |
data-url with abort controllerstabOpened, tabReady, eventClick, eventInput, etc.YaiTabs doubles as an application event hub. Add any event type and get automatic hooks:
const tabs = new YaiTabs({
events: {
setListener: {
'[data-yai-tabs]': ['click', 'keydown', 'input', 'change', 'submit']
}
}
});
// All events are automatically available as hooks
tabs.hook('eventClick', ({ event, target, container, action }) => {
console.log('Click action:', action); // Extracted from data-click
});
tabs.hook('eventInput', ({ event, target, container, action }) => {
console.log('Input action:', action); // Extracted from data-input
});
tabs.hook('tabOpened', ({ detail }) => {
console.log('Tab opened:', detail.id);
});
Multiple hooks per event:
tabs
.hook('tabOpened', (ctx) => trackAnalytics(ctx))
.hook('tabOpened', (ctx) => updateUI(ctx))
.hook('tabOpened', (ctx) => loadContent(ctx));
data-tab="1" or data-tab="2". And repeat the step in each pasted component. But set your expectations first, what’s your first thought? And share your final conclusion.License: MIT