fix: disable twoslash for cloudflare build

[jhcpeixoto]

Targets #8917.

The Cloudflare OpenNext build fails while collecting page data because the Cloudflare MDX config imports a VFS Twoslash setup, which pulls Node.js filesystem modules into the Worker bundle. This keeps syntax highlighting enabled on Cloudflare but disables Twoslash for that deployment target, and removes the now-unused VFS generator/dependencies.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nodejs-org	Ready	Preview	May 30, 2026 12:47am

[cursor]

PR Summary

Low Risk
Cloudflare-only behavior change; syntax highlighting remains, with Twoslash type hover/errors absent on that deployment only.

Overview
Cloudflare MDX now turns off Twoslash while keeping Shiki highlighting (wasm: false, twoslash: false), avoiding Node filesystem code in the Worker bundle during OpenNext page-data collection.

The VFS Twoslash path is removed for this target: create-vfs-twoslasher.mjs, the twoslash-fsmap generator scripts, and prebuild/predeploy/predev hooks that emitted generated/twoslash-fsmap.json. Dependencies twoslash and @typescript/vfs are dropped from platforms/cloudflare/package.json.

Other deployment targets (e.g. default/Vercel) are unchanged and still use Twoslash.

^{Reviewed by Cursor Bugbot for commit 15cb87e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[MattIPv4]

Why? I'm not sure I follow removing functionality instead of fixing it...

And, was this PR generated with AI assistance that you haven't declared? Your PR body originally had escaped newline characters which is usually a tell-tale sign of that.

[jhcpeixoto]

Why?

Is fix of other PR

[MattIPv4]

I don't think removing functionality is particularly a fix?

[avivkeller]

That generation was specifically added because it works on CF deployments. Removing it would not make sense.