Cache module of Riba.js


Keywords
Art+Code Studio, Riba, Rivets, tinybind, SPA, TypeScript, Browser, Cache
License
MIT
Install
npm install @ribajs/cache@2.0.0-rc.14

Documentation

Riba.js

Riba.js is a fork of Rivets.js, a lightweight data binding and templating system that facilitates building data-driven views. It is agnostic about every aspect of a front-end MV(C|VM|P) stack, making it easy to introduce it into your current workflow or to use it as part of your own custom front-end stack comprised of other libraries.

Documentation

You found the documentation source files on github.com/ribajs/doc or rendered on ribajs.com.

Yarn

We are using yarn to build and release Riba, so to test the demos please use yarn instead of npm.

Demos

For the different modules there are some demos, to start one of the demos go into the directory and execute it with yarn run start:

git clone --recurse-submodules https://github.com/ribajs/riba.git
cd riba/demos/core-each-item # replace core-each-item with a demo of your choice
yarn run start

Examples

There are a few Riba projects you can take a look at:

OctoberCMS v1.x

There are a few OctoberCMS v1.x themes which were developed using Riba:

Shopify Themes

Node.js

  • The Gymnasium Otterndorf Website was developed using Riba.js, Nest.js and Strapi. Riba.js is also used for the templates on the server side, and the custom elements are delivered with server side rendering (SSR).
  • The ParcelLab Shopify App is a small Shopify App and the dashboard / fronted is build with Riba.js.

Deno

Contributing

Clone

This branch contains submodules, to check out this repository with it submodules use the --recurse-submodules option:

git clone --recurse-submodules https://github.com/ribajs/riba.git

If you have already cloned this repository, you can also check out the submodules afterwards:

git submodule update --init --recursive --rebase --force

Bug Reporting

  1. Ensure the bug can be reproduced on the latest master.
  2. (optional) Submit a new demo oriented on the existing demos to illustrate the problem

Pull Requests

  1. Fork the repository and create a topic branch.
  2. Include tests that cover any changes or additions that you've made.
  3. Push your topic branch to your fork and submit a pull request. Include details about the changes as well as a reference to related issue(s).