Stuck on an issue?
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.
Libraries which depends on `localStorage`
See original GitHub issueBeta.11 basically drops localStorage support
localStorage will be lost as the url changes. We always recommend using the Storage API to avoid this issue.
I wonder what to do with 3rd-party libraries, which are relying on the localStorage and you can’t change that? For instance, aws-amplify.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
9 JavaScript Libraries for Working with Local Storage - SitePoint
localForage. This library, built by Mozilla, gives you a simple localStorage-like API, but uses asynchronous storage via IndexedDB or WebSQL. ...
Read more >Window.localStorage - Web APIs | MDN
The localStorage read-only property of the window interface allows you to access a Storage object for the Document 's origin; the stored data ......
Read more >local-storage-pro - npm
A Web storage spec compliant cross browser local storage library. ... There are different types of distributions depending on your use case.
Read more >LocalStorage, sessionStorage - The Modern JavaScript Tutorial
There are libraries that polyfill that API, based on localStorage , that make it available everywhere. Summary. Web storage objects localStorage ...
Read more >How to use localStorage from an imported library?
That depends on when and were the function is to be used. You can also use onMount outside of Svelte files, but of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah, it’s how @ptitjes says, it’s lost from beta 8 to beta 11, because it doesn’t use the localhost url anymore, nor http scheme, and the url changes because of that. But once you have beta 11 the url doesn’t change and you can use localStorage just fine. It doesn’t affect new apps neither, it’s just for apps migrating from beta 8 to beta 11
I believe it is meant as: data previously stored in
localStoragewill be lost at upgrade tobeta.11. You can still uselocalStorage.