fix(ext/node): ignore Node.js' --experimental-* flags when spawning child process

[EdamAme-x]

Closes #26349

[CLAassistant]

All committers have signed the CLA.

[bartlomieju]

Ignoring this error might not really help with running Wrangler in Deno. It appears they use new API from vm which is currently not available in Deno.

[EdamAme-x]

It will take more to get wrangler fully working...
However, this PR may help with compatibility.

[brandonweeks]

node:vm does not appear to be a dependency of any of the core wrangler workflows.

Patching out --experimental-vm-modules and running wrangler deploy with Deno works.

% deno run --allow-env --allow-net --allow-read --allow-run --allow-sys --allow-write --unstable-detect-cjs ~/Code/workers-sdk/packages/wrangler/wrangler-dist/cli.js versions upload

 ⛅️ wrangler 4.11.1
-------------------

🌀 Building list of assets...
✨ Read 4 files from the assets directory /Users/bweeks/Code/web/brandonweeks.github.io/dist
🌀 Starting asset upload...
No updated asset files to upload. Proceeding with deployment...
Total Upload: 0.32 KiB / gzip: 0.23 KiB
Worker Startup Time: 0 ms
No bindings found.
Uploaded holy-pine-54cf (2.75 sec)
Worker Version ID: 30c5d5d4-9ab5-4174-9916-5507bc9b9027

To deploy this version to production traffic use the command wrangler versions deploy

Changes to non-versioned settings (config properties 'logpush' or 'tail_consumers') take effect after your next deployment using the command wrangler versions deploy

Changes to triggers (routes, custom domains, cron schedules, etc) must be applied with the command wrangler triggers deploy

Given that, some variation of this change seems prudent. Would it make sense to add a deno run flag to allow specifying additional Node.js flags to ignore?

[bartlomieju]

Thanks