Andy-K-Sparklight / Alicorn

A high performance custom Minecraft launcher.
https://alc.pages.dev
GNU General Public License v3.0
43 stars 7 forks source link

chore(deps): bump @mui/material from 5.3.1 to 5.4.0 #105

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps @mui/material from 5.3.1 to 5.4.0.

Release notes

Sourced from @​mui/material's releases.

v5.4.0

Feb 1, 2022

A big thanks to the 22 contributors who made this release possible. Here are some highlights ✨:

@mui/material@5.4.0

Breaking changes

  • ​[core] Do not reexport Base from Material (#30853) @​michaldudak

    All Base components were exported from the @mui/material package and treated as stable even though the @mui/base package is in development. It could create a lot of confusion if developers start using Base components, depend on them, and demand quality found in "proper" Material components. We admit it was a mistake to reexport these components without marking them as unstable.

    Developers are still encouraged to evaluate the Base components, but they should do so by explicitly installing the @mui/base package.

    This is technically a breaking change as it removes a number of components from the @mui/material package. However, we believe that removing the components now and potentially breaking the codebases will do less harm than introducing "silent" breaking changes to Base components while continuing reexporting them from @mui/material.

    Note: the utility components, such as ClickAwayListener, NoSsr, Portal, and TextareaAutosize continue to be exported from both @mui/material and @mui/base.

    If you're encountering build errors after upgrading @​mui/material, do the following:

    1. Install @​mui/base: npm install @​mui/base or yarn add @​mui/base
    2. Make sure the version of @​mui/base match the version of @​mui/material
    3. Change the import paths of unstyled components from @​mui/material to @​mui/base, e.g.:
    - @import ButtonUnstyled from '@mui/material/ButtonUnstyled';
    + @import ButtonUnstyled from '@mui/base/ButtonUnstyled';
    

Changes

@mui/base@5.0.0-alpha.67

@mui/lab@5.0.0-alpha.67

... (truncated)

Changelog

Sourced from @​mui/material's changelog.

5.4.0

Feb 1, 2022

A big thanks to the 22 contributors who made this release possible. Here are some highlights ✨:

@mui/material@5.4.0

Breaking changes

  • ​[core] Do not reexport Base from Material (#30853) @​michaldudak

    All Base components were exported from the @mui/material package and treated as stable even though the @mui/base package is in development. It could create a lot of confusion if developers start using Base components, depend on them, and demand quality found in "proper" Material components. We admit it was a mistake to reexport these components without marking them as unstable.

    Developers are still encouraged to evaluate the Base components, but they should do so by explicitly installing the @mui/base package.

    This is technically a breaking change as it removes a number of components from the @mui/material package. However, we believe that removing the components now and potentially breaking the codebases will do less harm than introducing "silent" breaking changes to Base components while continuing reexporting them from @mui/material.

    Note: the utility components, such as ClickAwayListener, NoSsr, Portal, and TextareaAutosize continue to be exported from both @mui/material and @mui/base.

    If you're encountering build errors after upgrading @​mui/material, do the following:

    1. Install @​mui/base: npm install @​mui/base or yarn add @​mui/base
    2. Make sure the version of @​mui/base match the version of @​mui/material
    3. Change the import paths of unstyled components from @​mui/material to @​mui/base, e.g.:
    - @import ButtonUnstyled from '@mui/material/ButtonUnstyled';
    + @import ButtonUnstyled from '@mui/base/ButtonUnstyled';
    

Changes

@mui/base@5.0.0-alpha.67

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)