Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Persistent hyperdb in browser
See original GitHub issueI’ve been trying to get a persistent hyperdb to work in my browser for the past 2 days.
The problem is that hyperdb expects random-access-storage based storage as its backend, and the only existing implementation that works in the browser is random-access-memory, which is volatile. This would mean that everytime my browser tab is reloaded it will lose its content and when it connects to peers it will need to be reauthorized.
I’ve tried frankensteining together level-browserify and random-access-memory, but this is very error prone. Is there a backend for hyperdb that supports persistent browser storage? or maybe another way of preserving the key and replaying changes without breaking the database?
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@eklem you can try random-access-web as well: https://github.com/random-access-storage/random-access-web
I can’t quite remember (I never did finish that project) but I think I had success with random-access-idb