Convert given HTML into Virtual DOM object
Vite plugin to load html anywhere
Virtual HTML frames machinery
Parses well-formed HTML (meaning all tags closed) into an AST and back. quickly.
Webpack Virtual Modules
Virtual syntax highlighting for virtual DOMs and non-HTML things
A tiny but mighty list virtualization component, with zero dependencies 💪
HTML template for vite app, support flexible virtual URL.
Parses well-formed HTML (meaning all tags closed) into an AST and back. quickly.
Converts html into a vtree
Lightweight, robust, elegant virtual syntax highlighting using Prism
React Virtual List Component
A Vite plugin that takes the CSS and adds it to the page through the JS. For those who want a single JS file.
Morph a DOM tree to another DOM tree (no virtual DOM needed)
A diff for DOM elements, as client-side JavaScript code. Gets all modifications, insertions and removals between two DOM fragments.
React Virtual List Component
A low level parser for ANSI sequences.
Smooth scrolling for any amount of data
Load virtual modules from memory
🌱 Lightweight offline DOM
Angular DevKit - Core Utility Library
Virtual Background enables users to blur their background or replace it with a solid color or an image. This feature is applicable to scenarios such as online conferences, online classes, and live streaming. It helps protect personal privacy and reduces a
Hooks for virtualizing scrollable elements in React
Web Component for displaying a virtual/infinite list of items.
Proforma is a virtual document object model. This library allows you to output HTML for a virtual Proforma document.
A set of [mustache] templates extending [tla-trace-filter] -tool to create a self extracting achieve for API traces generated, when model checking formal models created by [tla-Sbuilder] -tool. Also includes Ruby classes to extract test cases from archive extract. Use case: Formal models, built using [tla-sbuilder], and model checked using [TLA+tools]], can generate /API Traces/, which represent end-to-end scenarios executing across system services in the formal model. An API Trace is composed of steps, with each step giving 1) a (formal) system state before the API call, 2) the API call exercised together with (formal model) value bindings of request parameters, 3) API response returned, and 4) the (formal) system state after the API call. A API Trace can be mapped to /Unit Tests/ on implementation with each Unit Test corresponding a step in the API Trace. After executing each of the individual Unit Tests, the aggregate result can be interpreted as an execution of a "virtual" System Test - considerably easier than managing the execution a System Test as a single unit. The purpose of =tla-trace-arch= GEM is create a self extracting archive, which can be safely distributed to system service developers for extracting API Trace Steps to create unit tests for the service being developed by the developer. Ref: - https://github.com/jarjuk/tla-trace-filter - https://mustache.github.io/mustache.5.html - https://github.com/jarjuk/tla-sbuilder - http://research.microsoft.com/en-us/um/people/lamport/tla/tools.html
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.