[Bug?]: Upgrading from v3.1.1 to v3.2.0 causes TS Webpack to hang without error/output

[awdyson]

Update: upgrading from node v14 to v16 fixed this for me.

---

Self-service

• I'd be willing to implement a fix

Describe the bug

Title says about as much as I can about the bug here.
No amount of "verbose" settings or command line flags were getting me more than dev-server's "wait until bundle finished".
I'm also really unsure as to why Yarn would cause an issue like this.
That said, running yarn set version stable and yarn before yarn start causes the issue, and the same set with 3.1.1 replacing stable fixes it.

I figured maybe there was an issue with directory references being "better-respected" now.
Something like / instead of ./ causing the whole filesystem to be parsed.
However, I combed through my code and couldn't find a path starting with /.

To reproduce

[removed as my repro wasn't applicable]

Environment

System:
    OS: macOS 11.6.2
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
  Binaries:
    Node: 14.16.1 - /private/var/folders/_1/3y0l6b0x0xd7_2vhtt4n089184gr2c/T/xfs-71cdc61f/node
    Yarn: 3.2.0 - /private/var/folders/_1/3y0l6b0x0xd7_2vhtt4n089184gr2c/T/xfs-183926a8/yarn
    npm: 7.11.2 - ~/.local/share/nvm/v14.16.1/bin/npm

Additional context

I like to keep my dependencies super up-to-date, but I haven't had time to work on this project for a couple months.
The above issue occurs with the latest package versions from 2 months ago and the latest versions from 2 minutes ago.

[merceyz]

Duplicate of #4157

[awdyson]

From the issue linked above, upgrading to node v16 fixed the issue for me.