Debian Patches

Status for node-mui-material/5.18.0+ds-2

Patch Description Author Forwarded Bugs Origin Last update
browserslist-stable-defaults.patch relax the "stable" browserslist target to "defaults" The upstream "stable" (and "legacy") browserslist environments pin exact
browser versions such as "op_mob 73". Debian's node-caniuse-lite database does
not know some of these exact versions and browserslist aborts the ESM build
with "Unknown version 73 of op_mob".
.
Only the "stable" environment is used by the Debian build (it produces the ESM
bundle); replacing its hand-pinned list with the tolerant "defaults" query
keeps the ESM output working. The exact browser target only influences how far
@babel/preset-env down-levels the output, which is not significant for the
packaged library.
Xavier Guimard <yadd@debian.org> not-needed 2026-07-20
drop-mui-base-tsref.patch drop the stale @mui/base project reference of @mui/material @mui/material 5.18 no longer imports @mui/base (grep of packages/mui-material/src
finds no @mui/base import), but its tsconfig.build.json still lists mui-base as
a TypeScript project reference. That drags @mui/base into the declaration build,
which in turn requires @floating-ui/react-dom -- not packaged in Debian -- and
fails the build. @mui/base is not built or shipped by this package, so the
reference is removed.
Xavier Guimard <yadd@debian.org> not-needed 2026-07-20
tsconfig-skiplibcheck.patch enable skipLibCheck for the declaration build Debian ships @emotion 11.10 whose serialize/types/index.d.ts is written against
an older csstype than the node-csstype 3.1.3 available here; type-checking it
raises hundreds of TS2411 "not assignable to string index type" errors inside
emotion's own declaration files. skipLibCheck skips type-checking of .d.ts
files, which is appropriate: this build only emits @mui/material's own
declarations and does not need to re-verify its dependencies' typings.
Xavier Guimard <yadd@debian.org> not-needed 2026-07-20
textarea-mutable-ref.patch make TextareaAutosize's heightRef a mutable ref @mui/material 5.18 is type-checked upstream against @types/react 19, where
useRef<T>(null) yields a mutable ref. Debian ships @types/react 18.3, where the
same call resolves to the readonly RefObject<T> overload, so the assignment to
heightRef.current fails with "Cannot assign to 'current' because it is a
read-only property". Widening the ref to number | null selects the mutable
overload and keeps the runtime behaviour identical.
Xavier Guimard <yadd@debian.org> not-needed 2026-07-20

All known versions for source package 'node-mui-material'

Links