introduction tutorial failed

[ChaosInTheCRD]

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

Description

Hi there 👋

I am getting started with docusaurus and so I followed the introduction.

After running npx create-docusaurus@latest my-website classic I got the output:

[INFO] Creating new Docusaurus project...
[INFO] Installing dependencies with npm...
[ERROR] ShellJSInternalError: ENOENT: no such file or directory, open '/var/folders/s0/gq2w894d50787bdzpzqcb76m0000gn/T/shelljs_b027ad55a2c30709a641'

It created the ./my-website, so I followed the next steps of entering the directory and running npx docusaurus start, but unfortunately it left me with another error:

npm ERR! could not determine executable to run

Finally, I found a stack overflow comment that suggested running npm install in the project directory. Thankfully this worked! Maybe it'd be worth adding something to this tutorial so other users don't face similar issues.

Thanks!

Self-service

• I'd be willing to address this documentation request myself.

[slorber]

Please try again running npx create-docusaurus@latest my-website classic

This is not supposed to error and print:

[ERROR] ShellJSInternalError: ENOENT: no such file or directory, open '/var/folders/s0/gq2w894d50787bdzpzqcb76m0000gn/T/shelljs_b027ad55a2c30709a641'

And this is supposed to do the npm install for you.

All other users do not have problem running this command, so maybe it's a temporary bug or a bug related to your own system.

---

If the problem happens again, make sure you are using Node.js 18+, and try to generate the project into another folder.

And share us your exact env (OS, node etc) because with outthat it's impossible to investigate anything.

[aMacDawg]

@slorber I have experienced this exact same problem on Apple Silicon gen1 (2020) with the ERROR] ShellJSInternalError: ENOENT: no such file or directory, open '/var/folders/s0/gq2w894d50787bdzpzqcb76m0000gn/T/shelljs_b027ad55a2c30709a641' error.

My workaround was to then run npm init which seemed to solve the problem, but when I tried to yarn deploy so I could deploy this to my github page, I got this same complaint from yarn (on latest 1.22.x version)

System settings
Node 21.3.x
NPM 10.2.x
Mac OS: 13.0.1
Apple Silicon (2020) 16GB

Please let me know if you need more information, I am not sure why this issue was closed so abruptly, I was disappointed to keep stumbling into these problems especially after the project was spoken of so highly by various colleagues!

[aMacDawg]

@ChaosInTheCRD what Node version were you using? I had installed 21.3.0 using nvm specifically for this, but I wonder @slorber if it's better to use node v18.x.x?

[slorber]

@aMacDawg I'm on Node 18, yes it's better to use a Node LTS, usually more stable (v18 or v20)

Now if there's an issue with Node 21 we should probably investigate and fix it too, because it's likely to become a Node 22 bug later.

Are you both using Node 21?

[slorber]

I can confirm the issue under node 21.3.0, but it's not there anymore in node 21.5.0, so it is likely a nodejs temporary bug

[ChaosInTheCRD]

Sorry for the slow response!

I can confirm that I am on node version 21.3.0. I will update for sanity when I upgrade to confirm that the problem has gone away.