ansgar grunseid

@Sajma27 Did you mean to close this PR?

Wonderful report. Thank you. I created https://github.com/gruns/ImmortalDB/issues/37, which will help resolve this.

This is tricky. ImmortalDB strives to remain agnostic of the underlying key:value storage implementation(s). As such, it's not currently a requirement that underlying key:value stores provide method(s) to iterate through...

> What if you make a requirement for all stores to provide a clear() method, but > also have the convention that it can return false meaning that it does...

All sensible suggestions. I tried to find a workaround for this particular aspect > every cookie set is sent to the server on every request without success. When a cookie's...

> The docs aren't clear on how I can instantiate a DB omitting cookies. > > I don't transpile my code. I want to use the .min.js file directly. Can...

> I'd suggest disabling the cookie storage option by default, making it opt-in. A fair compromise could be: by default, `ImmortalDB`'s data stores don't include `CookieStore`; instead just `IndexedDbStore`, `LocalStorageStore`,...

In short, ImmortalDB's capacity depends on the stores used. For example, if `CookieStore` is used, which it is by default, storage per key is limited by the browser's cookie storage...

Thus far, I've run a simple webserver in the root directory ``` $ http-server -p 5050 & $ google-chrome "http://localhost:5050/testing/test.html" ``` and tested manually via `testing/test.html`. This is, obviously, boorish....

> IIn the PR I did for using lodash functions instead of the whole library, I > added a webpack-server to make the test in the browser easier using npm...