Brand new project fails to compile - throws errors

[fuzing]

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

Prerequisites

• I'm using the latest version of Docusaurus.
• I have tried the npm run clear or yarn clear command.
• I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
• I have tried creating a repro with https://new.docusaurus.io.
• I have read the console error message carefully (if applicable).

Description

Brand new project installed using nodejs v18.7.

Installation and subsequent commands:

npx create-docusaurus@latest <project-name> --typescript
cd <project-name>
npm start

Results in the following errors:

TypeError: /home/Projects/some-project/node_modules/@docusaurus/theme-common/lib/components/Details/index.js: Cannot read properties of undefined (reading '0')
    at run.next (<anonymous>)
    at transform.next (<anonymous>)
TypeError: /home/Projects/some-project/node_modules/@docusaurus/theme-common/lib/index.js: Cannot read properties of undefined (reading '0')
    at run.next (<anonymous>)
    at transform.next (<anonymous>)
TypeError: /home/Projects/some-project/node_modules/@docusaurus/theme-common/lib/internal.js: Cannot read properties of undefined (reading '0')
    at run.next (<anonymous>)
    at transform.next (<anonymous>)
TypeError: /home/Projects/fsome-project/node_modules/@docusaurus/utils-common/lib/index.js: Cannot read properties of undefined (reading '0')
    at run.next (<anonymous>)
    at transform.next (<anonymous>)
client (webpack 5.75.0) compiled with 4 errors

Reproducible demo

No response

Steps to reproduce

npx create-docusaurus@latest <project-name> --typescript
cd <project-name>
npm start

Expected behavior

Per installation/getting started docs, this should work

Actual behavior

Throws errors:

TypeError: /home/Projects/some-project/node_modules/@docusaurus/theme-common/lib/components/Details/index.js: Cannot read properties of undefined (reading '0')
    at run.next (<anonymous>)
    at transform.next (<anonymous>)
TypeError: /home/Projects/some-project/node_modules/@docusaurus/theme-common/lib/index.js: Cannot read properties of undefined (reading '0')
    at run.next (<anonymous>)
    at transform.next (<anonymous>)
TypeError: /home/Projects/some-project/node_modules/@docusaurus/theme-common/lib/internal.js: Cannot read properties of undefined (reading '0')
    at run.next (<anonymous>)
    at transform.next (<anonymous>)
TypeError: /home/Projects/fsome-project/node_modules/@docusaurus/utils-common/lib/index.js: Cannot read properties of undefined (reading '0')
    at run.next (<anonymous>)
    at transform.next (<anonymous>)
client (webpack 5.75.0) compiled with 4 errors

Your environment

• Public source code: development/private right now
• Public site URL: development/private right now
• Docusaurus version used: 2.3.1 (latest)
• Environment name and version (e.g. Chrome 89, Node.js 16.4):
• Operating system and version (e.g. Ubuntu 20.04.2 LTS): Ubuntu 22.04 LTS

Self-service

• I'd be willing to fix this bug myself.

[andysm1th]

I am also experiencing this same problem

[andysm1th]

This also happens when not using Typescript, so:

npx create-docusaurus@latest docusaurus-test classic

I am using Node v18.14.0

I've also tried with the pnpm and yarn package managers, they return the same error as posted above by fuzing.

[fuzing]

ditto - tried with yarn and pnpm - same result. Folks using the discord channel seeing the same thing.

[zph]

I'm seeing the same outcome in the following new scenarios:

1. node v19.6.0
2. node v18.14.0
3. Installation failed in same way using npx create-docusaurus@latest my-website classic (after the desired project name failed to work), with and without the typescript flag

[Tandashi]

For Reference / Duplicate of #8688
Also describes a workaround for the meantime

Using the yarn.lock(https://codesandbox.io/p/sandbox/github/facebook/docusaurus/tree/main/examples/classic?file=%2Fyarn.lock) and installing with yarn install --force --pure-lockfile works. Looks like a dependency issue

[Josh-Cena]

I'm going to close this as a duplicate of #8688