chore: upgrade frontend-build, patch font-awesome, use React.StrictMode, refactor dashboard tabs #777
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
@edx/frontend-build
to latest (v12.8.57).font-awesome
viapatch-package
(docs).font-awesome
.React.StrictMode
(docs). By doing so, we should be able to identify and fix any issues now to make future React upgrades easier (and to take advantage of React features like concurrent rendering). Upon running the application locally withReact.StrictMode
, the behavior doesn't appear to be any different, so this feels like a safe enough change for now.React.StrictMode
only impacts the application when running in development; does not affect production builds.DashboardPage
tabs to rely on an array as its children due to the conditional feature flags used as currently implemented. If those feature flags arefalse
, it would break theTabs
component which expects every child node to be aTab
component (i.e., not aboolean
).For all changes
Only if submitting a visual change