Map integration for Famo.us (google-maps, leaflet, open-layers & mapboxgl)
Generates and consumes source maps
Generates and consumes source maps
Store information about any JS value in a side channel, using a Map
Fixes stack traces for files with source maps
concatenative mapdashery
Is this value a JS Map? This module works cross-realm/iframe, and despite ES6 @@toStringTag.
Fixes stack traces for files with source maps
No description provided.
Persistent ordered mapping from strings
Converts a source-map from/to different formats and allows adding/changing properties.
[Experimental] - 🚇 File crawling, watching and mapping for Metro
Generate source maps
extracts inlined source map and offers it to webpack
Automatically cleanup expired items in a Map
Map and Set with automatic key interning
Packages @jridgewell/trace-mapping and @jridgewell/gen-mapping into the familiar source-map API
Data library for istanbul coverage objects
Basic cache object for storing key-value pairs.
Map over promises concurrently
Map `visit` over an array of objects.
Retrieves a name:pathname Map for a given workspaces config
A thing that is a lot like ES6 `Map`, but without iterators, for use in environments where `for..of` syntax and `Map` are not available.
Analyze and debug space usage through source maps
A Ruby implementation of the famous Doubly Linkedlist data structure with support to the Enumerable methods such as `each`, `to_a`, `map`, etc. following ruby idioms. Supports Queue operations as well as Stack operations. A Linkedlist is efficient in many specific cases(eg:- Queue operations) than other data structures such as Array.
Reactive is a desktop application framework that gives everything needed to create database-backed applications according to the Model-View-Control pattern of separation. Reactive is highly inspired and also uses code of Rails, the famous Web-Framework for ruby. In Reactive, the model is handled by what's called an object-relational mapping layer. Reactive doesn't impose any ORM, you may choose the one you like but Reactive defaults to Active Record. This means it has baked in support for it, without forcing you to use it. The view part is independant of Reactive, this means that the application has to choose a view provider and feed it into Reactive. This leads to complete freedom for the GUI part. View providers are packaged as gems, so that it is easy for the developer to choose and install them. Look for reactive_view_* to discover some view providers (at this early alpha stage, only reactive_view_wx is available) The controller is part of Reactive and is loosely coupled to the view. Simple convention set up the link.