stateSanitizer removed from latest update?

[RaiMX]

Hello,

previous version had devtools stateSanitizer option to sanitize large data in Redux Devtools. Now it is gone. What should we use instead?

[dai-shi]

Is it type only issue?

[dai-shi]

Could you look into which change broke it?

[RaiMX]

Could you look into which change broke it?

Unfortunately I'm not that skilled.
I gues it is somehow related to #3413

[dai-shi]

Hm, that was type only issue.

Let's ask @grigoriy-reshetniak for help.

@RaiMX Can you create a minimal reproduction?

[RaiMX]

Hm, that was type only issue.

Let's ask @grigoriy-reshetniak for help.

@RaiMX Can you create a minimal reproduction?

While creating reproduction, I found out that I was wrong.

False alarm.
Everything work fine. My apologies. v5.0.12 is good.
This discussion can be closed.

[grigoriy-reshetniak]

Mistakes happens, thanks for the update!

[sueun-dev]

This was a typing regression introduced in v5.0.11. The PR #3362 tightened the DevtoolsOptions type by removing some any casts, which accidentally made the type too strict. Options that previously worked (like stateSanitizer, serialize, etc.) started throwing TypeScript errors like:

Object literal may only specify known properties, and 'stateSanitizer' does not exist in type 'DevtoolsOptions'

The fix landed in v5.0.12 with PR #3414, which correctly extends the Redux DevTools Config type again.

So upgrading should restore it:

npm install zustand@latest
# or
pnpm add zustand@latest

After upgrading to v5.0.12+, stateSanitizer should work as before since it's part of the Redux DevTools Extension's Config type that DevtoolsOptions extends:

const useStore = create(
  devtools(
    (set) => ({ /* your state */ }),
    {
      name: 'myStore',
      stateSanitizer: (state) => ({
        ...state,
        largeData: '<<OMITTED>>',
      }),
    }
  )
)

To answer @dai-shi's question too — yes, it was a type-only regression, not a runtime behavior change.