Bug? Using provider with atom that derive from atomsWithStorage trigger twice in jotai v2

[devnomic]

Using provider with atom that derive from atomsWithStorage trigger twice with initial value as first.

Minimal repro:

• Click the change id button.
• Click the toggle show button

jotai v2:
https://codesandbox.io/s/rough-dawn-45558b?file=/src/App.tsx

jotai v1: (same code, work as expected).
https://codesandbox.io/s/headless-sun-bnxrvb?file=/src/App.tsx

[dai-shi]

Yes, it's a design choice.

jotai/docs/guides/migrating-to-v2-api.mdx

Line 213 in c4ef100

- `atomWithStorage` util's `delayInit` is removed as being default.

(That one line is not very helpful though...)

See also: #1737

[devnomic]

I see,
But why it only happens when i wrap it with provider tag?
So what should i do if i want the same behavior like v1?

My case i have a component that has a props that will initialize the atom. basically it's #826 so i need provider to wrap the component.

[dai-shi]

You are remounting the entire Provider. That's why.

If you want the sync behavior with localStorage, here's the simple, valid, and flexible solution:

jotai/docs/guides/persistence.mdx

Lines 14 to 22 in dae4418

	const strAtom = atom(localStorage.getItem('myKey') ?? 'foo')
	const strAtomWithPersistence = atom(
	(get) => get(strAtom),
	(get, set, newStr) => {
	set(strAtom, newStr)
	localStorage.setItem('myKey', newStr)
	}
	)

https://codesandbox.io/s/currying-browser-0mps6p?file=/src/App.tsx

[devnomic]

Thank you!