TypeScript: Object deconstruction with alias and default value does not work

[kostia1st]

What version of Next.js are you using?

12.0.2

What version of Node.js are you using?

16.4.0

What browser are you using?

Edge, Chrome

What operating system are you using?

Windows 11

How are you deploying your application?

next dev

Describe the Bug

Here's a TypeScript code snippet

  const value = { ho: [1, 2] };
  const { ho: hey = [] } = value;
  console.log(hey);

Output is []

Must be [1, 2]

Once you remove the "default value" or aliasing - it works normally.

tsconfig.json -> compilerOptions -> "target": "es5", "module": "commonjs", "lib": ["dom", "dom.iterable", "esnext"]

Reverting back to "next": "11.1.2" immediately fixes the issue.

Expected Behavior

Should be deconstructing objects properly, assigning the default value only when the provided one is not defined.

I can just imagine it's somehow connected with the new Rust compiler.

To Reproduce

See above

[kostia1st]

From my perspective this issue is critical - because it does not yell to the developer that something's not working, instead it silently works improperly.

If I had my billing implemented in TS/node.js, and poor E2E-testing applied, I'd be having 3 weeks of corrupt data by now. Cannot imagine someone's using version 12 of next.js in production right now.

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.