The TypeScript variant for the classic template is missing

[ghost]

🐛 Bug Report

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

Running npm init docusaurus@latest my-website classic --typescript produces the identical files as running the same script without the --typescript flag. It looks like the classic-typescript folder contains the same files as classic, which might be the cause.

Have you read the Contributing Guidelines on issues?

Yes.

Steps to reproduce

1. Run npm init docusaurus@latest my-website classic.
2. Run npm init docusaurus@latest my-website classic --typescript.
3. Compare the files in the directories created by the two commands above.

Expected behavior

The project created by running the command with the --typescript flag should have TypeScript set up.

Actual behavior

The project created by running the command with the --typescript flag has the same setup as the one created without the --typescript flag.

Your environment

• Docusaurus version used: 2.0.0-beta.7
• Environment name and version (e.g. Chrome 78.0.3904.108, Node.js 10.17.0): Node.js 16.11.1, npm 8.1.0
• Operating system and version (e.g. Ubuntu 20.04.2 LTS): macOS 11.6

Reproducible demo

https://codesandbox.io/s/github/facebook/docusaurus/tree/main/examples/classic-typescript

[Josh-Cena]

With the new npm init syntax you would need to use extra -- (https://docusaurus.io/docs/next/installation#scaffold-project-website):

npm init docusaurus@latest my-website classic -- --typescript

I know it's tricky because we didn't fix it in the versioned docs. We should

[shirakaba]

Using Docusaurus 2.0.0-beta.8, I actually provided the extra -- to forward options, but providing it was precisely what caused the failure:

# npm v6.14.7, node v16.1.0:
# ❌ This fails to produce the TypeScript template
npm init docusaurus@latest my-website classic -- --typescript

# npm v6.14.7, node v16.1.0
# ✅ This successfully produces the TypeScript template
npm init docusaurus@latest my-website classic --typescript

Comparing the npm v6 and npm v7 docs for npm init, it appears to be from npm v7 onwards that npm init requires passing -- for forwarding options.

As npm v6 comes with node v16, which is the "current" version of node at the time of writing and begins active long-term support from 26th Oct 2021, I feel the docs should reflect two sets of instructions: one for npm v7 and above, and another for versions below that.

[Josh-Cena]

Yes, @slorber just realized after the beta-8 release that there's an inconsistency between npm v6 and v7, but he's currently unavailable. Let's see what's the best solution to this.

[slorber]

npm 6/7 issue will be fixed in #5797