virtual parameters setting
Webpack Virtual Modules
React Virtual List Component
Smooth scrolling for any amount of data
React Virtual List Component
Load virtual modules from memory
Compile ES2015 default and rest parameters to ES5
Parses well-formed HTML (meaning all tags closed) into an AST and back. quickly.
Transform optional chaining operators to workaround https://crbug.com/v8/11558
Angular DevKit - Core Utility Library
Hooks for virtualizing scrollable elements in React
A Vite plugin that takes the CSS and adds it to the page through the JS. For those who want a single JS file.
`rrdom` is a virtual dom library that is used by `rrweb` to replay DOM mutations. It is a standalone library that can be used to create a virtual dom tree and apply patches to the real dom. It's used in `rrweb` to optimize replay performance especially wh
A Map based TypeScript Virtual File System.
A batched diff-based DOM rendering strategy
[](https://www.npmjs.com/package/prosemirror-virtual-cursor)
Core filesystem primitives: Node, Link, File, Superblock
A tiny but mighty list virtualization component, with zero dependencies 💪
Morph a DOM tree to another DOM tree (no virtual DOM needed)
Virtual scroll for for Angular Material Table
Express style path to RegExp utility
No description provided.
filesystem utilities for the npm cli
Create and parse HTTP Content-Type header
A simple and lightweight parameter validation library that leverages ActiveModel to provide a clean interface for handling parameters with real and virtual fields.
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.