misc: avoid using fs.realpathSync in website

[Zamiell]

fixes yarn start, from @Josh-Cena

[facebook-github-bot]

Hi @Zamiell!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

[Josh-Cena]

For context: this doesn't work on virtually every Windows machine. See #7052 for one.

fs.realpathSync is really not very useful because it just points to the original directory. We may well just use the original one, then.

[netlify]

✅ [V2]

Built without sensitive environment variables

Name	Link
🔨 Latest commit	f71466f
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/628efada9ffc9100081563fc
😎 Deploy Preview	https://deploy-preview-7496--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	PWA	Report
/	🟠 83	🟢 100	🟢 100	🟢 100	🟢 90	Report
/docs/installation	🟠 85	🟢 99	🟢 100	🟢 100	🟢 90	Report

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[Josh-Cena]

Thanks!

[slorber]

I don't understand, how do we test for our symlinked dir support now?

[Josh-Cena]

How is fs.realpathSync testing anything in practice, though? It always evaluates to "_dogfooding/_docs tests" on machines that support it. On machines that don't support symlinks (i.e. all Windows machines), it always causes an obscure error that I have to teach them to fix. Previously when we had resolve.symlinks: false for Webpack, it seems more worthwhile to test, but now, it's simply not an API of ours anymore, more like a user-land workaround.

[slorber]

ok 👍 true

[mahendranjayavel]

Hi, not sure if this is a known issue.

I am using:

macOS
Docusaurus 3.7.0
Node.js 20.19.1
Homebrew Git
And I am still getting spawn EBADF from ShellJS, even after setting NO_SHELLJS=true.
I think I am hitting a low-level file descriptor bug in ShellJS on macOS that Docusaurus hasn't fully mitigated in 3.7.0, especially during lastUpdateTime Git metadata collection.

Any thoughts? I badly need to keep the Git lastUpdateTime config for my docs setup.

[slorber]

@mahendranjayavel fixed in #11163 recently :)

By chance we are releasing v3.8 right now. It's already on npm, and the release blog post is going to be published asap.