jStorage VS cookies.js

Compare jStorage vs cookies.js and see what are their differences.

jStorage

jStorage is a simple key/value database to store data on browser side (by andris9)

cookies.js

🍫 Tastier cookies, local, session, and db storage in a tiny package. Includes subscribe() events for changes. (by franciscop)
Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
jStorage cookies.js
- 1
1,538 2,380
- -
0.0 0.0
almost 4 years ago almost 5 years ago
JavaScript JavaScript
The Unlicense MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

jStorage

Posts with mentions or reviews of jStorage. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning jStorage yet.
Tracking mentions began in Dec 2020.

cookies.js

Posts with mentions or reviews of cookies.js. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-03-01.
  • DDD Is Overrated
    2 projects | news.ycombinator.com | 1 Mar 2021
    Sure you might not be able to write 100% of the documentation in one go and then the code, but AFAIK that's neither the goal or the intention of DDD, it's more like "document a bit, write a bit, repeat".

    The way I do it is first write a draft of the documentation, of how I want the API to look like. Then check if that basic code is possible (which I can predict most of the times based on experience), then write some more docs or methods. When writing a lib I normally already know where I want to use it, so I can put example snippets from how I want to use it as the documentation first and then try to implement those methods.

    Examples of libraries I've written mostly this way:

    - https://github.com/franciscop/brownies

    - https://github.com/franciscop/files

    - https://github.com/franciscop/backblaze

What are some alternatives?

When comparing jStorage and cookies.js you can also consider the following projects:

basket.js - A script and resource loader for caching & loading files with localStorage

js-cookie - A simple, lightweight JavaScript API for handling browser cookies

localForage - 💾 Offline storage, improved. Wraps IndexedDB, WebSQL, or localStorage using a simple but powerful API.

jquery-cookie

Cookies - JavaScript Client-Side Cookie Manipulation Library

store.js - Cross-browser storage for all use cases, used across the web.

WatermelonDB - 🍉 Reactive & asynchronous database for powerful React and React Native apps ⚡️

cross-storage - Cross domain local storage, with permissions

lawnchair.js - A lightweight clientside JSON document store,

sql.js - A javascript library to run SQLite on the web.