You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other packages are updated to minor versions. (No breaking changes)
Breaking Change Notes
Docusaurus v3
New version uses @mdx-js/react v3. The syntax should now escape the < and { characters with a backslash in .md files. In current TruBudget typedoc generated api docs, this is not being done. The fix is to add the package @types/react to the TruBudget api folder, which will generate correct .md files.
New version has some structural changes, thus the @type imports had to be renamed (such as from DocPage to DocRoot) More info: Relevant Docusaurus PR
New version uses react v18 so react is also upgraded.
Whatever package was providing the classnames, is no longer providing it as a dependency. That's why it is now added manually into dependency list.
Packages plugin-content-docs and @docusaurus/theme-search-algolia are removed from dependencies. These already come with the classic preset of the Docusaurus and are configured under docusaurus.config.js
The text was updated successfully, but these errors were encountered:
egdmrsy
changed the title
Bump React version to v18
Bump dependency versions and handle breaking changes
Nov 20, 2023
Version updates
Breaking Change
Breaking Change Notes
Docusaurus v3
@mdx-js/react v3
. The syntax should now escape the < and { characters with a backslash in .md files. In current TruBudget typedoc generated api docs, this is not being done. The fix is to add the package@types/react
to the TruBudget api folder, which will generate correct .md files.classnames
, is no longer providing it as a dependency. That's why it is now added manually into dependency list.plugin-content-docs
and@docusaurus/theme-search-algolia
are removed from dependencies. These already come with the classic preset of the Docusaurus and are configured under docusaurus.config.jsThe text was updated successfully, but these errors were encountered: