Skip to content

Conversation

@mctylr-gh
Copy link
Contributor

Update mui and emotion to current minor versions and patches.

Update Material UI (a React component library that implements Google's Material Design) from 5.14.12 to 5.18.0

This is the most recent release of MUI 5.x.

Material UI v6 does support React 17, but it has some breaking changes, that I suspect may affect us.

This was not initiated for any known bugs in Bitburner, but to reduce the "distance" between the current stable release of Material UI, and our dependencies without introducing breaking changes.

MUI 5.15.x and 5.16.x contains numerous (~12-20) bug fixes, but doesn't appear to have any breaking changes.

MUI 5.17.0 - I believe this doesn't affect us.
MUI 5.17.1 - fixes a layout bug.

MUI 5.18.0 is a backport of CSS layers feature from MUI v7.

The Emotion package for writing CSS using JavaScript / React, is updated from 11.11.x to 11.14.x, as I believe it is used only in connection with the MUI packages. Again updates appear minor; bug fixes, and migrated to using TypeScript, with no breaking changes noted.

mctylr-gh and others added 4 commits September 26, 2025 07:35
MUI from 5.14.12 to 5.18.0

While not initiated for any known bugs in Bitburner.

MUI 5.15.x and 5.16.x contains numerous bug fixes, but
doesn't appear to have any breaking changes.

[MUI 5.17.0](https://github.com/mui/material-ui/releases/tag/v5.17.0)
I believe this doesn't affect us.
[MUI 5.17.1](https://github.com/mui/material-ui/releases/tag/v5.17.1)
fixes a layout bug.

[MUI 5.18.0](https://github.com/mui/material-ui/releases/tag/v5.18.0)
is a backport of CSS layers feature from MUI v7.

The Emotion package is
[updated](https://github.com/emotion-js/emotion/releases) from
11.11.x to 11.14.x, as I believe it is used only in connection with
the MUI packages. Again updates appear minor, with no breaking changes
noted.
@catloversg
Copy link
Collaborator

I don't see any regression bugs in UI, but I think you need to test the change in package-lock.json.

I'm not sure why, but when I make the same changes, my package-lock.json is slightly different from yours (node_modules/@mui/material/node_modules/react-is).

How to test:

  • git clone https://github.com/bitburner-official/bitburner-src.git
  • Edit package.json
  • npm i

I tested on 2 machines (Windows 10 + VM Debian 13) with nodejs v22.20.0 and npm 10.9.3. Please test it again on your machine.

@mctylr-gh
Copy link
Contributor Author

mctylr-gh commented Oct 8, 2025

It is because I made the commit on Sep 26 when react-is@19 was 19.1.1, and then Facebook released React 19.2.0 on Oct 1.

npm cleaninstall didn't update the react-is@19 to 19.2.0. But manually deleting node_modules and doing npm install does produce your expected results.

@d0sboots d0sboots merged commit f12fc38 into bitburner-official:dev Oct 8, 2025
6 checks passed
@mctylr-gh mctylr-gh deleted the mui-518 branch October 9, 2025 08:31
@mctylr-gh mctylr-gh restored the mui-518 branch October 9, 2025 08:32
@mctylr-gh mctylr-gh deleted the mui-518 branch October 9, 2025 08:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants