Search Results for "dom"

Solid is a declarative JavaScript library for creating user interfaces. Instead of using a Virtual DOM, it compiles its templates to real DOM nodes and updates them with fine-grained reactions. Declare your state and use it throughout your app, and when a piece of state changes, only the code that depends on it will rerun. Check out our intro video or read on! Fine-grained updates to the real DOM. Declarative data: model your state as a system with reactive primitives. ...

Next-generation testing framework powered by Vite. Reuse Vite's config and plugins - consistent across your app and tests. But Vitest is not required. Expect, snapshot, coverage, and more - migrating from Jest is straightforward. Out-of-box ESM, TypeScript and JSX support powered by esbuild.

An extensible text editor framework that does things differently. Lexical is comprised of editor instances that each attach to a single content editable element. A set of editor states represent the current and pending states of the editor at any given time. Lexical is designed for everyone. It follows best practices established in WCAG and is compatible with screen readers and other assistive technologies. Lexical is minimal. It doesn't directly concern itself with UI components, toolbars...

...It comes with smart selector strategies that can, e.g. using the react$ command, fetch React components by its component name and filter it by its props or states. A similar command called $shadow provides the ability to fetch elements within the shadow DOM of a web component.

...Slate's core logic assumes very little about the schema of the data you'll be editing, which means that there are no assumptions baked into the library that'll trip you up when you need to go beyond the most basic use cases. The document model used for Slate is a nested, recursive tree, just like the DOM itself. This means that creating complex components like tables or nested block quotes are possible for advanced use cases. But it's also easy to keep it simple by only using a single level of hierarchy.

Cycle’s core abstraction is your application as a pure function main() where inputs are read effects (sources) from the external world and outputs (sinks) are write effects to affect the external world. These I/O effects in the external world are managed by drivers, plugins that handle DOM effects, HTTP effects, etc. The internals of main() are built using Reactive Programming primitives, which maximizes separation of concerns and provides a fully declarative way of organizing your code. The dataflow is plainly visible in the code, making it readable and traceable. Cycle.js apps are made of pure functions, which means you know they only take inputs and generate predictable outputs, without performing any I/O effects. ...