chrome.storage.local.get doesn't return the initial values

[Othmanosx]

when providing an initial value to the createChromeStorageStateHookLocal hook, and trying to access the data from chrome.storage.local.get, it returns undefined instead of the initial false.
P.S.: the hook is already mounted by the timechrome.storage.local.get was called.

export const SETTINGS_KEY = 'settings';
const INITIAL_VALUE = {
  isDark: false,
};

export const useSettingsStore = createChromeStorageStateHookLocal(SETTINGS_KEY, INITIAL_VALUE);

  chrome.storage.local.get([SETTINGS_KEY], async function (result) {
      console.log(result.isDark) // undefined
  });

[onikienko]

It's the behavior of chrome.storage.
It doesn't set an init/ial value. It only uses it if no value stored.

// say isDark not stored in storage yet (undefined)
// getting isDark and providing initial value
const options = await chrome.storage.sync.get({isDark: true});
constole.log(options.isDark); // true (initial value used)
// getting isDark without initial value
const options1 = await chrome.storage.sync.get('isDark');
constole.log(options1.isDark); // undefined (we did not set isDark yet and did not provide init value)

[lukmanuthmanabubakr]

Why I’d like to work on this issue

I have experience with React and Chrome Extensions, and I’ve worked with chrome.storage for persisted state. The issue occurs because chrome.storage.get() doesn’t save the initial value , it only returns it when given as a default. This explains why createChromeStorageStateHookLocal returns undefined instead of the expected initial state.

My plan to solve it

1. Update the hook so it writes the initial value to storage if the key is missing.
2. Ensure chrome.storage.local.get([KEY]) always returns the correct value.
3. Add tests for both cases (existing vs missing keys).

Why I’m the right person
I have hands-on experience building with React hooks, Chrome APIs (storage.local, sync, session), and debugging async persistence issues. I can provide a clean, well-documented PR with tests to make this hook behave more predictably for developers.