Data Components for building Reactive Maps Interfaces
Data Components for building Reactive Maps Interfaces
Reactive Extensions for modern JavaScript
Reactive utilities for Embla Carousel
Source maps support for istanbul
Library for composing asynchronous and event-based operations in JavaScript
Wrapper for the loading of Google Maps JavaScript API script in the browser
Resolve package.json exports & imports maps
InfoBox for React.js Google Maps API
Marker Clusterer for React.js Google Maps API
React.js Google Maps API integration
React components and hooks for the Google Maps JavaScript API
Fixes stack traces for files with source maps
SolidJS Primitives to manage creating event listeners.
Webpack loader that adjusts source maps
React Native Mapview component for iOS + Android
A collection of helpers that aim to simplify using reactive primitives outside of reactive roots, and managing disposal of reactive roots.
Node.js client library for Google Maps API Web Services
A WebGL interactive maps library
React Components for building map UIs
An svg map chart component built with and for React
Use deck.gl as a custom Google Maps overlay
CLI and JS library for uploading source maps to Bugsnag
Primitives for creating small reactive objects that doesn't change their shape over time - don't need a proxy wrapper.
Provides a local MVC machinery to handle requests of the reactive application. The machinery is mapped to what is done in RubyOnRails, so you'll have rails like controllers, rails like views and helpers. Because Reactive is Model and View agnostic, this plugin alone will not do the complete job.
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.