Adding a single relative require() call turns other calls into a crazy game of whack-a-mole in JS project with Node

[DanielRosenwasser]

Steps

mkdir ughrepro
cd ughrepro
mkdir src
code .

Create the file ./src/index.js:

// @ts-check

const net = require("net");
const path = require("path");
const readline = require("readline");
const stream = require("stream");

If at this point nothing seems off (ATA has taken effect and you can jump to definitions on each of those paths), then try reloading the editor or just wait a few seconds.

If you suddenly get errors, try inserting a space into one of the paths. That path will still be invalid but the rest will suddenly work.

[DanielRosenwasser]

This is even stranger. One space in the bogus require() call fixes all the other imports, but two causes them all to break again.

[DanielRosenwasser]

Workaround 😢