A base class for your Coffeescript projects
Adds Coffeescript support to your Nuxt app
esload CoffeeScript module
Unfancy JavaScript
browserify plugin for coffeescript with support for mixed .js and .coffee files
coffee loader module for webpack
decaffeinate fork of the CoffeeScript implementation
decaffeinate fork of the CoffeeScript implementation
A drop-in substitute for the browser native localStorage API that runs on node.js.
a promise-based ftp client for node.js
Bundle CoffeeScript with Esbuild
IcedCoffeeScript
TypeScript definitions for coffeescript
IcedCoffeescript for Node-Red
Cypress preprocessor for bundling JavaScript via webpack with dependencies included and support for various ES features, TypeScript, and CoffeeScript
A finite state machine (FSM) implementation for node.js
CoffeeScript coverage tool
React JSX support for Coffeescript
Validate and visualize dependencies. With your rules. JavaScript, TypeScript, CoffeeScript. ES6, CommonJS, AMD.
a command line option parser that will make you smile
Move your CoffeeScript source to modern JavaScript.
binary heap (priority queue) algorithms (ported from Python's heapq module)
URL tooling for assetgraph
A better AST for CoffeeScript, inspired by CoffeeScriptRedux.
Don't wrap Coffeescript compiled output in IIFEs if es6 module is being used
Convert CoffeeScript classes to AngularJS modules Write less JavaScript. Write less CoffeeScript. Write less Angular.
ruby-coffee-react is a bridge to the npm coffee-react-transform module, which transforms CJSX (Coffeescript with React JSX-style markup) into valid Coffeescript. If you want to use CJSX with Rails/Sprockets, see the sprockets-coffee-react gem.
Preprocessor for Coffeescript with React JSX (CJSX). This gem makes it easy to integrate this into the Rails asset pipeline or other Sprockets chains. If you want to use CJSX without Sprockets, see the coffee-react gem, or the coffee-react npm module.
Preprocessor for Coffeescript with React JSX (CJSX). This gem makes it easy to integrate this into the Rails asset pipeline or other Sprockets chains. If you want to use CJSX without Sprockets, see the coffee-jsx gem, or the coffee-jsx npm module. This is an update version of sprockets-coffee-jsx gem.
RSence is a different and unique development model and software frameworks designed first-hand for real-time web applications. RSence consists of separate, but tigtly integrated data- and user interface frameworks. RSence could be classified as a thin server - thick client system. Applications and submobules are installed as indepenent plugin bundles into the plugins folder of a RSence environment, which in itself is a self-contained bundle. A big part of RSence itself is implemented as shared plugin bundles. The user interface framework of RSence is implemented in high-level user interface widget classes. The widget classes share a common foundation API and access the browser's native API's using an abstracted event- and element layer, which provides exceptional cross-browser compatibility. The data framework of RSence is a event-driven system, which synchronized shared values between the client and server. It's like a realtime bidirectional form-submission engine that handles data changes intelligently. On the client, changed values trigger events on user interface widgets. On the server, changed values trigger events on value responder methods of server plugin modules. It doesn't matter if the change originates on client or server, it's all synchronized and propagated automatically. The server framework is implemented as a high-level, modular data-event-driven system, which handles delegation of tasks impossible to implement using a client-only approach. Client sessions are selectively connected to other client sessions and legacy back-ends via the server by using the data framework. The client is written in Javascript and the server is written in Ruby. The client also supports CoffeeScript for custom logic. In many cases, no custom client logic is needed; the user interfaces can be defined in tree-like data models. By default, the models are parsed from YAML files, and other structured data formats are possible, including XML, JSON, databases or any custom logic capable of producing similar objects. The server can connect to custom environments and legacy backends accessible on the server, including software written in other languages.
RSence is a different and unique development model and software frameworks designed first-hand for real-time web applications. RSence consists of separate, but tigtly integrated data- and user interface frameworks. RSence could be classified as a thin server - thick client system. Applications and submobules are installed as indepenent plugin bundles into the plugins folder of a RSence environment, which in itself is a self-contained bundle. A big part of RSence itself is implemented as shared plugin bundles. The user interface framework of RSence is implemented in high-level user interface widget classes. The widget classes share a common foundation API and access the browser's native API's using an abstracted event- and element layer, which provides exceptional cross-browser compatibility. The data framework of RSence is a event-driven system, which synchronized shared values between the client and server. It's like a realtime bidirectional form-submission engine that handles data changes intelligently. On the client, changed values trigger events on user interface widgets. On the server, changed values trigger events on value responder methods of server plugin modules. It doesn't matter if the change originates on client or server, it's all synchronized and propagated automatically. The server framework is implemented as a high-level, modular data-event-driven system, which handles delegation of tasks impossible to implement using a client-only approach. Client sessions are selectively connected to other client sessions and legacy back-ends via the server by using the data framework. The client is written in Javascript and the server is written in Ruby. The client also supports CoffeeScript for custom logic. In many cases, no custom client logic is needed; the user interfaces can be defined in tree-like data models. By default, the models are parsed from YAML files, and other structured data formats are possible, including XML, JSON, databases or any custom logic capable of producing similar objects. The server can connect to custom environments and legacy backends accessible on the server, including software written in other languages.
No description provided.
No description provided.
No description provided.