node package manager

ractive

Next-generation DOM manipulation

Ractive.js - Next-generation DOM manipulation

It's a JavaScript library for building reactive user interfaces in a way that doesn't force you into a particular framework's way of thinking. It takes a radically different approach to DOM manipulation - one that saves both you and the browser unnecessary work.

Features include...

  • Data-binding, with a beautiful declarative syntax.
  • Event handling that doesn't make you tear your hair out.
  • Flexible and performant animations and transitions.
  • And much more!

To get a feel for how it will make your life as a web developer easier, visit ractivejs.org, follow the interactive tutorials, or try the 60 second setup.

If you don't find what you're looking for in the docs, here are other channels you can ask:

If you'd like to include an example in your issue, this fiddle has a convenient minimal setup that has easily switchable Ractive versions.

Pull requests and issues are always welcome! Please read CONTRIBUTING.md to learn how to contribute.

If you want to hack on Ractive, the first step is to fork the repo. Then do the following commands.

# Clone your fork of the repo
git clone https://github.com/YOUR_USERNAME/ractive
 
# Move into the repo directory
cd ractive
 
# Install the dependencies
npm install
 
# Run a server for development
npm start

Navigate to localhost:4567. You'll see:

  • ractive-legacy.js - A build of Ractive that includes legacy browser support.

  • sandbox - Contains some template files to help with debugging.

  • test - The test suite.

To start development, copy the sandbox/sample, following the instructions therein. After the initial build, any subsequent changes will result in fast incremental rebuilds. If you're using Chrome, you can use the LiveReload plugin.

The development server is served by gobble and is still in development. Please report any Gobble-related bugs to Gobble's issue tracker. Thanks!

To build, the following must be met:

  • A real shell. Linux and OS X should be good. Windows needs MSYS or something similar at least on the path.

  • On Windows, if you get an EINVAL when running the tests, you may need to update the phantomjs script in the node_modules/.bin to use { stdio: 'inherit' } when spawning the child process instead of manually piping afterwards.

To run a complete build including linting, testing and minification:

npm run build

Tested successfully in IE9+ and all modern browsers. For legacy browser support, use the builds with suffix legacy in the filename. These builds include polyfills and other essential features required by Ractive. If your experience differs please let us know!

All builds are published to the default npm registry and can thus be accessed from the lovely unpkg CDN:

  • https://unpkg.com/ractive is the latest stable unminified version of Ractive.
  • https://unpkg.com/ractive/ractive.min.js is the latest stable minified version of Ractive.
  • The rest of the builds play out as you would expect too: ractive-legacy.js, ractive.runtime.js, ractive-legacy.min.js, ractive.runtime.min.js
  • https://unpkg.com/ractive@0.7.3 is the unminified build of Ractive v0.7.3
  • You can also pull specific builds for specific versions e.g. https://unpkg.com/ractive@0.7.3/ractive.min.js
  • The latest pre-release build in a series is tagged e.g. v0.8-dev or v0.9-dev, starting with v0.8. This dev tag will point to the latest released version in a series if there is no dev build e.g. immediately after a release.
  • dev builds are periodically published to npm with a pre-release version like 0.8.1-build-1, and the latest dev build is tagged edge.

Copyright (c) 2012-16 Rich Harris and contributors. Released under an MIT license.