"const" was transformed to "var" when target is "esnext"

🔎 Search Terms

transform, const, var, target, ECMA, esnext

🕗 Version & Regression Information

• This is the behavior in every version I tried from Version 5.4 to Version 5.7.0-dev.20240904

⏯ Playground Link

No response

💻 Code

export const cilBlurLinear : string [ ] = [  ,  ] 
const [ ,  ] = cilBlurLinear;

🙁 Actual behavior

The JS code generated by tsc is as follows:

"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
exports.cilBlurLinear = void 0;
exports.cilBlurLinear = [,];
var ;

🙂 Expected behavior

“const” should be translated as "const" instead of "var", as the target in my configuration file is "esnext".

Additional information about the issue

tsconfig.json:

{
  "compilerOptions": {
    "target": "ESNext",
    "module": "esnext",
    "moduleResolution": "Node",
    "esModuleInterop": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true,
    "lib": ["es2023","dom"],
    "noEmitOnError":true,
    "force":true,
    "strict":true
  },
  "include": [
    "TScorpus/*"
  ],
  "exclude": [
    "node_modules"
  ]
}

Start by reproducing the provided code with tsc and the shown tsconfig.json, then inspect the compiler's handling of const destructuring when the target is ESNext. Done means the emitted JavaScript preserves const and does not produce the invalid var output; add a regression test for this case if the repository's existing compiler tests identify a suitable location.