Disable MAX_WRITE_OPERATIONS_PER_HOUR when developing

Question

Is there any way to disable the MAX_WRITE_OPERATIONS_PER_HOUR setting for Chrome storage during development? I'm completely blocked right now because I hit the max while testing a new feature. It's really frustrating.

Answer 1

Use chrome.storage.local instead of chrome.storage.sync during development.

Synchronized storage is rate-limited, because everything is sent to Google's servers. Local Chrome storage (not to be confused with localStorage) is only saved to the user's local file system and not throttled.