📦 Upgrade to Docusaurus v3

[bradystroud]

for issue #12

These docs were helpful https://docusaurus.io/docs/migration/v3
This issue also helped facebook/docusaurus#8940 (comment)

• Updated Docusaurus Packages:

  • @docusaurus/core from 2.2.0 to 3.3.2
  • @docusaurus/preset-classic from 2.2.0 to 3.3.2
  • @docusaurus/module-type-aliases from 2.2.0 to 3.3.2

• Updated React Packages:

  • react from ^17.0.2 to ^18.3.1
  • react-dom from ^17.0.2 to ^18.3.1

• Updated TinaCMS Packages:

  • @tinacms/cli to ^1.5.29
  • tinacms to ^1.5.20

• Updated MDX Packages:

  • @mdx-js/react from ^1.6.22 to ^3.0.1

• Updated Other Dependencies:

  • clsx from ^1.2.1 to ^2.1.1
  • prism-react-renderer from ^1.3.5 to ^2.3.1
  • title to ^3.5.3

• Updated Node Engine Requirement:

  • node from >=16.14 to >=18.0

This update enhances compatibility with the latest versions, ensuring improved performance and new features.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
tinasaurus	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 30, 2024 1:12am

[ncn-ssw]

issue: When I attempt to run yarn && yarn tina as per the README, I receive the following error:

$ docusaurus start
[INFO] Starting the development server...

[ERROR] Error: Docusaurus could not load module at path "/home/ncn/Source/Tina/tinasaurus/tinasaurus/docusaurus.config.js"
Cause: lightCodeTheme is not defined
    at loadFreshModule (/home/ncn/Source/Tina/tinasaurus/tinasaurus/node_modules/@docusaurus/utils/lib/moduleUtils.js:36:15)
    at loadSiteConfig (/home/ncn/Source/Tina/tinasaurus/tinasaurus/node_modules/@docusaurus/core/lib/server/config.js:35:62)
    ... 4 lines matching cause stack trace ...
    at async Command.start (/home/ncn/Source/Tina/tinasaurus/tinasaurus/node_modules/@docusaurus/core/lib/commands/start/start.js:22:28) {
  [cause]: ReferenceError: lightCodeTheme is not defined
      at /home/ncn/Source/Tina/tinasaurus/tinasaurus/docusaurus.config.js:152:14
      at evalModule (/home/ncn/Source/Tina/tinasaurus/tinasaurus/node_modules/jiti/dist/jiti.js:1:256443)
      at jiti (/home/ncn/Source/Tina/tinasaurus/tinasaurus/node_modules/jiti/dist/jiti.js:1:254371)
      at loadFreshModule (/home/ncn/Source/Tina/tinasaurus/tinasaurus/node_modules/@docusaurus/utils/lib/moduleUtils.js:33:16)
      at loadSiteConfig (/home/ncn/Source/Tina/tinasaurus/tinasaurus/node_modules/@docusaurus/core/lib/server/config.js:35:62)
      at async Promise.all (index 1)
      at async loadContext (/home/ncn/Source/Tina/tinasaurus/tinasaurus/node_modules/@docusaurus/core/lib/server/site.js:33:97)
      at async loadSite (/home/ncn/Source/Tina/tinasaurus/tinasaurus/node_modules/@docusaurus/core/lib/server/site.js:126:21)
      at async createReloadableSite (/home/ncn/Source/Tina/tinasaurus/tinasaurus/node_modules/@docusaurus/core/lib/commands/start/utils.js:46:16)
      at async Command.start (/home/ncn/Source/Tina/tinasaurus/tinasaurus/node_modules/@docusaurus/core/lib/commands/start/start.js:22:28)

This is on Ubuntu 22 running under WSL with a fresh repository checked out as follows:

git clone "https://github.com/tinacms/tinasaurus.git"
cd tinasaurus/
git checkout upgrade
yarn && yarn tina

[bradystroud]

Hey @ncn-ssw

thanks - fixed in the latest commit

[ncn-ssw]

🚀 LGTM
Tested with Yarn and NPM
Some dependency issues raised with NPM install, but they are caused by TinaCMS dependencies and will be corrected in due course.