Building @mui/base breaks due to deprecated csstype.Property.ColorAdjust

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Current behavior 😯

When running ttsc -b I am seeing the following errors:

node_modules/@mui/base/SliderUnstyled/useSlider.d.ts:146:54 - error TS2694: Namespace '"/Users/william.pengc3.ai/Projects/c3vsce/c3vsce/extension/node_modules/csstype/index".Property' has no exported member 'ColorAdjust'.

146             colorAdjust?: import("csstype").Property.ColorAdjust | undefined;
                                                         ~~~~~~~~~~~

node_modules/@mui/base/SliderUnstyled/useSlider.d.ts:651:65 - error TS2694: Namespace '"/Users/william.pengc3.ai/Projects/c3vsce/c3vsce/extension/node_modules/csstype/index".Property' has no exported member 'ColorAdjust'.

651             WebkitPrintColorAdjust?: import("csstype").Property.ColorAdjust | undefined;
                                                                    ~~~~~~~~~~~

Found 2 errors.

Looking into csstype I see that they released a new version today from MDN data, which does not have the color-adjust property anymore.

MDN docs also suggest that color-adjust is gone, as the page redirects instead to print-color-adjust.

The solution is probably to update import("csstype").Property.ColorAdjust to import("csstype").Property.PrintColorAdjust, but in any case, this is breaking our builds.

Expected behavior 🤔

No errors should be outputted

Steps to reproduce 🕹

Steps:

1. Include @mui/base in dependencies
2. Run ttsc -b

Context 🔦

We are trying to build our project with ttsc -b which has an indirect dependency on @mui/base

Your environment 🌎

`npx @mui/envinfo`

  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

[Anubiso]

found a workaround and added

"resolutions": {
    "csstype": "3.0.10"
  }

to the package.json, now it builds again

[c3-william-peng]

Yup, after upgrading @mui/material and @mui/icons-material to ^5.5.0 the issues were resolved. Closing this issue as the upgraded versions have resolved this.