Open Source JavaScript Libraries for Mac

Inferno is an insanely fast, React-like library for building high-performance user interfaces on both the client and server. React-like API, concepts and component lifecycle events. Switch over easily with inferno-compat. One of the fastest front-end frameworks for rendering UI in the DOM, making 60 FPS on mobile possible. Isomorphic rendering on both client and server, along with fast-booting from server-side renders. Inferno doesn't have a fully synthetic event system like React does. Inferno has a partially synthetic event system, instead opting to only delegate certain events (such as `onClick`). Inferno doesn't support React Native. Inferno was only designed for the browser/server with the DOM in mind. Inferno doesn't support legacy string refs, use `createRef` or callback `ref` API. Inferno provides lifecycle events on functional components. This is a major win for people who prefer lightweight components rather than ES2015 classes.

Simply download and attach your js, css with bootstrap. Customize by Initializing various options and modules. Summernote is licensed under MIT and maintained by the community. Integrate it with any back-end. 3rd parties available in django, rails, angular. Bootstrap uses certain HTML elements and CSS properties which require HTML5 doctype. Summernote uses the Open Source libraries jQuery and Bootstrap, if you are using the Boostrap 3 or 4 versions of Summernote, or just jQuery if you use the Lite version of Summernote. Summernote allows you to customize the toolbar. You can compose a toolbar with pre-shipped buttons. Air-mode give an interface without the Toolbar. To reveal popover Toolbar, select a text where you want to modify. Simply turn on airMode and just focus on text. Styles change according to Bootstraps Theme. The editor uses the Bootswatch Themes based on Bootstrap 3, you can also do the same with Bootstrap 4.

nivo provides a rich set of dataviz components, built on top of the awesome d3 and Reactjs libraries. Several libraries already exist for React d3 integration, but just a few provide server side rendering ability and fully declarative charts. In order to use nivo, you have to install the @nivo/core package and then choose some of the scoped @nivo packages according to the charts you wish to use. Given an array of data series having an id and a nested array of points (with x, y properties), it will compute the line for each data series. All datum having null x or y will be treated as holes, thus portions of the corresponding line will be skipped. You can fully customize it using the circleComponent property to define your own, if you wish to do so you should have a look at the default SVG component to get started. Bar chart which can display multiple data series, stacked or side by side. Also supports both vertical and horizontal layout, with negative values descending below the x axis.

Workbox is a set of libraries that can power a production-ready service worker for your Progressive Web App. Stop waiting on the network! You can improve your web app's performance by caching and serving your files, powered by a service worker. Even on an unreliable connection, your web app can still work using the right runtime caching strategies. Looking to build a progressive web app? Workbox makes it easy to create an offline first experience. Workbox is a library that bakes in a set of best practices and removes the boilerplate every developer writes when working with service workers. Precaching, runtime caching, strategies, request routing, background sync, and helpful debugging. Wish you could rely on Google Fonts being available offline after the user has visited your site? Add a quick rule to serve them from the cache. Make your JS and CSS fast by returning the assets from the cache, while making sure they are updated in the background for the next use.

React Rainbow is a collection of components that will reliably help you build your application in a snap. Give it a hack and let us know what you think. We designed each component with i18n in mind. Any new component or feature we may add in the future has to be able to work fully in different locales. Proper documentation based on interactive examples to help you understand the features of each component. We know how important it for you is to test your UI. Our npm package provides a webdriver.io page object for almost every component. Our components are test infected. We like to test our components as much as possible.

The Closure Library is a broad, well-tested, modular, and cross-browser JavaScript library. You can pull just what you need from a large set of reusable UI widgets and controls, and from lower-level utilities for DOM manipulation, server communication, animation, data structures, unit testing, rich-text editing, and more. The Closure Library is server-agnostic and is intended for use with the Closure Compiler. The Closure Library serves as the base JavaScript library for many Google products. Now that the Closure Library is open source, more and more developers outside Google are integrating the library in their own projects. If you are developing a large or growing application, you may benefit from the Closure Library's breadth. A well-tested library can insulate you from cross-browser compatibility issues and the minutiae of client-side programming, letting you focus on the fun stuff.

Build automation and Package management system

Currently, each babel plugin in the babel ecosystem requires that you configure it individually. This is fine for things like language features but can be a frustrating overhead for libraries that allow for compile-time code transformation as an optimization. babel-plugin-macros defines a standard interface for libraries that want to use compile-time code transformation without requiring the user to add a babel plugin to their build system (other than babel-plugin-macros, which is ideally already in place). There is cpu usage/time overhead; the client needs to run the code to generate these classes every time the page loads. There is code bundle size overhead; the client needs to receive a CSS parser in order to generate these class names, and shipping this makes the amount of js the client needs to parse larger. Eval-ing out code at compile time that will be baked into the runtime code, for instance, to get a list of directories in the filesystem.