store.js
cookies.js
Our great sponsors
store.js | cookies.js | |
---|---|---|
6 | 1 | |
13,978 | 2,380 | |
- | - | |
0.0 | 0.0 | |
3 months ago | almost 5 years ago | |
JavaScript | JavaScript | |
MIT License | MIT License |
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.
store.js
-
Why dont we simply persist state in local storage, instead of using global state management
it's not made up, feel free to look it up. In older versions if the site was in a private window, writing something to localStorage would throw an exception. Was a pain in the ass and caused a lot of bugs. https://developer.apple.com/forums/thread/71593 https://news.ycombinator.com/item?id=17231508 https://github.com/marcuswestin/store.js/issues/42
-
Webpacker vs import maps : any thoughts ?
Some javascript libraries require you to configure them using webpack. For example, https://github.com/marcuswestin/store.js/ , if you want to use sessionstorage only without anything else. You need to rebuild the library using webpack. If you can tinker with building libraries and providing custom builds that suit your need and load them into importmap, then it is better to use importmap.
-
Vuex State data empty after reloading the page
I'm using store package to persist data after page reload.
-
Are mixins shared/single instance, or one instance for each component that uses the mixin?
store is basically a localStorage wrapper. If you want your data to persist even if on page reload, you might consider using it.
-
How to persist only a few state items with localstorage?
I've been using store, it's basically a localStorage wrapper.
-
Deployed my first React project.. yes, a Pokedex.
and the pokemon user can catch is saved using session based local storage, Store js (https://github.com/marcuswestin/store.js)
cookies.js
-
DDD Is Overrated
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?
localForage - 💾 Offline storage, improved. Wraps IndexedDB, WebSQL, or localStorage using a simple but powerful API.
js-cookie - A simple, lightweight JavaScript API for handling browser cookies
jStorage - jStorage is a simple key/value database to store data on browser side
jquery-cookie
lockr - A minimal API wrapper for localStorage
lawnchair.js - A lightweight clientside JSON document store,
WatermelonDB - 🍉 Reactive & asynchronous database for powerful React and React Native apps ⚡️
basil.js - The missing Javascript smart persistent layer
basket.js - A script and resource loader for caching & loading files with localStorage