API
The InDom API is organized by core areas such as element selection, event handling, value IO, traversal, DOM updates, attributes, styles and collection utilities. Browse the sections below to explore each method in detail, understand its behavior and see practical usage examples.
InDom.getOne(selector, container?)
InDom.get(selector, container?)
InDom.getById(id)
new InDom(source)
InDom.onReady(fn)
.getValue(container?)
InDom.getValues(...args?)
.setValue(value, container?)
.on(type, fn?, opts?)
.onRemove(fn)
.off(type?, fn?)
.getElement() / .el()
.remove()
.is(selector)
.getParent(selector?)
.getSelfOrParent(selector)
.getNext(selector)
.getPrev(selector)
.append(...children)
.prepend(...children)
.after(...siblings)
.before(...siblings)
.setHtml(content)
.getHtml()
.setData(key, value)
.getData(key)
.hasData(key)
.removeData(key)
.setAttr(key, value)
.getAttr(key)
.hasAttr(key)
.removeAttr(key)
.getBox()
.getOuterBox()
.getRelativeBox()
.getOffsetBox()
.addClass(...names)
.hasClass(name)
.removeClass(...names)
.setStyle(propertyOrMap, value?)
.getStyle(...properties?)
InDomArray inherited methods
.each(fn)
.filter(selectorOrFn)
Next: getOne »
Modern DOM Power
for TypeScript, ESM & Plain JS
3.8KB JavaScript library that simplifies DOM manipulation
with a clean, chainable API for events, data, inputs harvesting, and more.
Automatic Cleanup,
Leak-Proof by Design
Events and state are cleared when elements leave the DOM,
even if removal happens outside InDom.
Cleaner Code,
Better Ergonomics
Get the InDom object directly in callbacks.
One element, one instance.
Works With Your Existing Stack
Use InDom on its own or alongside any library or framework,
its architecture ensures a seamless integration.