[material-ui][Slider] Incorrect warning: "Invalid prop value of type string supplied to MuiSliderValueLabel, expected number"

[joshkel]

Steps to reproduce

Link to live example: https://stackblitz.com/edit/react-2yokah?file=Demo.tsx

Steps:

1. Load the page with the console open.

Current behavior

The console shows an unnecessary / incorrect warning:

Warning: Failed prop type: Invalid prop value of type string supplied to MuiSliderValueLabel, expected number.

Expected behavior

No warnings.

Context

Possibly relevant information:

• This issue is new in 6.1.4.
• Slider.js's assignment of SliderValueLabel.propTypes was added in 6.1.4 (due to [core] Fix proptypes generation when multiple components per file #44058).
• SliderValueLabel's own propTypes, SliderValueLabel's implementation, and valueLabelFormat's type declaration allow any node, not just numbers.
• SliderValueLabel's type declaration requires a number, which seems inconsistent / too restrictive.

Your environment

npx @mui/envinfo

``` System: OS: macOS 15.0.1 Binaries: Node: 18.20.2 - ~/.nvm/versions/node/v18.20.2/bin/node npm: 10.5.0 - ~/.nvm/versions/node/v18.20.2/bin/npm pnpm: Not Found Browsers: Chrome: 129.0.6668.101 Edge: 129.0.2792.89 Safari: 18.0.1 npmPackages: @emotion/react: 11.13.3 @emotion/styled: 11.13.0 @mui/base: 5.0.0-beta.59 @mui/core-downloads-tracker: 6.1.4 @mui/icons-material: 6.1.4 @mui/lab: 6.0.0-beta.12 @mui/material: 6.1.4 @mui/private-theming: 6.1.4 @mui/styled-engine: 6.1.4 @mui/system: 6.1.4 @mui/types: 7.2.18 @mui/utils: 6.1.4 @mui/x-date-pickers: 7.20.0 @mui/x-internals: 7.20.0 @mui/x-tree-view: 7.20.0 @types/react: ^18.3.11 => 18.3.11 react: ^18.3.1 => 18.3.1 react-dom: ^18.3.1 => 18.3.1 typescript: ^5.6.3 => 5.6.3 ```

Search keywords: MuiSliderValueLabel SliderValueLabel propTypes

[github-actions]

This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

Note

@joshkel How did we do? Your experience with our support team matters to us. If you have a moment, please share your thoughts in this short Support Satisfaction survey.

[thenick775]

Has this been released?

[ZeeshanTamboli]

Has this been released?

Not yet. The fix will be available in the next release.