This PR updates our front end libraries to the latest versions. A few libraries that we don't use were also removed
Changes Made
All of our libraries were updated to the latest version using npm update. This command does not update packages with new major semantic versions (ex. going from 2.x.x to 3.x.x), since these changes are breaking, so those had to be done manually
For libraries with major semantic version updates, the docs were referenced and breaking changes were addressed accordingly. Some libraries that we don't use were removed as well. The libraries with major version changes and the libraries that were removed are listed below
A authorizationParams prop was introduced to the provider. Basically, we need to specify some of the existing Auth0Provider props such as audience and redirectUri in a new object prop called authorizationParams
Some of the properties in authorizationParams are now snake case (ex. redirectUri is now redirect_uri)
Autocomplete now has some new props we should check out, we may be able to use them
The color prop on Typography is not a system prop anymore. According to the docs, some system colors are still accessible using this prop, so it was a bit confusing on what this means.. I think it means that you can't access all theme colors through this prop anymore, only the ones they provide? Either way, I don't think anything broke for us
A lot of things were deprecated in this release too. Deprecated APIs won't break anything for now, but support for them are often removed in the next major release version, so we should slowly migrate away from them
The big thing that affects us is that they are changing how inner element overrides work. TLDR, we have to swap from using the InputProps prop to using the new slotProps prop instead. I have changed some of our InputProps to use their new API.
A few other props were affected, such as the old components prop and componentsProps prop, as shown in their docs. I don't think we use many of these other than InputProps, but this is just something to look out for
Their system props are also deprecated in favor of the sx prop. I don't think we use many of these, but this is also something to look out for
@types/node
I couldn't really find docs for this but I think nothing is broken lol
The value prop has to be of the same type as your date adapter now. For us, we need to wrap our date objects in the datejs() parser. Also had to install datejs library
The renderInput prop is deprecated, we should use the slotProps prop now
Related Issues
Resolves #132
Summary
This PR updates our front end libraries to the latest versions. A few libraries that we don't use were also removed
Changes Made
All of our libraries were updated to the latest version using
npm update. This command does not update packages with new major semantic versions (ex. going from 2.x.x to 3.x.x), since these changes are breaking, so those had to be done manuallyFor libraries with major semantic version updates, the docs were referenced and breaking changes were addressed accordingly. Some libraries that we don't use were removed as well. The libraries with major version changes and the libraries that were removed are listed below
Libraries with Major Updates
auth0-react
authorizationParamsprop was introduced to the provider. Basically, we need to specify some of the existingAuth0Providerprops such asaudienceandredirectUriin a new object prop calledauthorizationParamsauthorizationParamsare now snake case (ex.redirectUriis nowredirect_uri)@mui/material, @mui/icons-material
Autocompletenow has some new props we should check out, we may be able to use themcolorprop onTypographyis not a system prop anymore. According to the docs, some system colors are still accessible using this prop, so it was a bit confusing on what this means.. I think it means that you can't access all theme colors through this prop anymore, only the ones they provide? Either way, I don't think anything broke for usInputPropsprop to using the newslotPropsprop instead. I have changed some of ourInputPropsto use their new API.componentsprop andcomponentsPropsprop, as shown in their docs. I don't think we use many of these other thanInputProps, but this is just something to look out forsxprop. I don't think we use many of these, but this is also something to look out for@types/node
typescript
vite
mui-x-date-picker
valueprop has to be of the same type as your date adapter now. For us, we need to wrap our date objects in thedatejs()parser. Also had to installdatejslibraryrenderInputprop is deprecated, we should use theslotPropsprop nowreduxjs/toolkit, react-redux
Libraries Removed
redux-coreis already bundled in withredux-toolkit, so we don't need thisredux-thunkis already bundled in withredux-toolkit, so we don't need thisScreenshots
No additional screenshots
Testing Instructions
No additional testing instructions
Special Notes for Your Reviewer(s)
No additional notes