TanStackOSS
    table
    fix(table-core): guard Array.isArray before index access in range autoRemove fns filterFn_between, filterFn_betweenInclusive, and filterFn_inNumberRange all had: autoRemove: (val: any) => testFalsy(val) || (testFalsy(val[0]) && testFalsy(val[1])) When a scalar (non-array) value like `99` is passed, `val[0]` and `val[1]` are both `undefined`. testFalsy(undefined) === true, so the second branch evaluates to `(true && true)` === true and the filter is immediately removed — even though 99 is a perfectly valid, non-empty filter value. Root-cause: numeric columns default to the `inNumberRange` filter function (auto-selected in column_getAutoFilterFn). Calling `col.setColumnFilter(99)` hits this path and the filter silently vanishes (issue #5949). Fix: add `Array.isArray(val) &&` so the index checks only run when val is actually an array. The testFalsy(val) head still removes undefined/null/''. Closes #5949
    nx run-many --targets=build --exclude=examples/**
Succeeded
CI Pipeline Execution1 run failed

nx run-many --targets=build --exclude=examples/**

Click to copy
Linux
4 CPU cores
read access token used
893b01876353
7%

Cache hits

1 of 15 tasks used cache.

Get faster results

Learn how to enable distribution.

Atomizer enabled

15 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools