-
Notifications
You must be signed in to change notification settings - Fork 30.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: clarify Web Storage behavior #53871
Comments
Hello sir, can you assign this Issue to me. I want to start my contribution journey and I think I can handle this issue |
We don't typically assign issues. If you want to work on this, just open a PR 😄 |
PR submitted. |
Hi Colin, a quick question here, I am trying to figure out where the 10MB quota comes from in node (if you don't mind pointing out for me). Deno has its own implementation of |
Sure. It comes from here. |
Ohh I see, thanks! A follow up question, should there be a test case for it? |
Thanks for giving more context on the WPT tests! I think I should've asked a bit more specific, should there be a test for testing 10mb quota in node? Given the fact it is up to individual implementors. Hope my question is not disturbing though 🙏 |
I guess it wouldn't hurt. I would recommend not doing repeated writes like the WPT tests though. That approach works because they don't know what the upper bound will be. Since we know Node's upper limit, we can do it in just a few writes. |
Closed by #53881 |
Affected URL(s)
https://nodejs.org/api/globals.html, https://nodejs.org/api/cli.html
Description of the problem
I think that we should clarify some behaviors of Web Storage in Node.js vs. browsers.
--localstorage-file
as its origin.Other things that would be good to note:
For reference, here are the Deno docs on Web Storage.
The text was updated successfully, but these errors were encountered: