Wrong scope's variable is used after SWC compilation

[patrick-entinux]

Describe the bug

Hi, I submitted a bug a few days ago, thank you for looking into that bug. 🙇 I am running the same project through SWC today too, I just came across this now, got a runtime error because a totally different variable was used than expected.

Input code

Not sure if it has any effect in this case, but this is in a TypeScript project, by the way.

const categories = [{ key: "apple" }, { key: "banana" }, { key: "strawberry" }];

const item = "some item";

const catNames = categories.reduce((a, item) => {
  return { ...a, [item.key.toString()]: item };
}, {});

Here was the SWC output:

"use strict";
const categories = [
    {
        key: "apple"
    },
    {
        key: "banana"
    },
    {
        key: "strawberry"
    }
];
const item = "some item";
const catNames = categories.reduce((a, item1)=>{
    return {
        ...a,
        [item.key.toString()]: item1
    };
}, {
});

Config

{
  "env": {
    "targets": {
      "node": 10
    }
  },
  "jsc": {
    "parser": {
      "syntax": "typescript",
      "tsx": true,
      "decorators": false,
      "dynamicImport": false
    }
  },
  "module": {
    "type": "commonjs"
  }
}

Expected behavior
A clear and concise description of what you expected to happen.

I expected the item.key.toString() line to get its item value from the parameter of the reduce() callback, not the other root level item.

"use strict";
const categories = [
    {
        key: "apple"
    },
    {
        key: "banana"
    },
    {
        key: "strawberry"
    }
];
const item = "some item";
const catNames = categories.reduce((a, item1)=>{
    return {
        ...a,
-         [item.key.toString()]: item1
+         [item1.key.toString()]: item1
    };
}, {
});

Hope this is clear? If any questions/clarifications, happy to add more info, thanks.

Version
The version of @swc/core: 1.2.35

Additional context
Add any other context about the problem here.

[swc-bot]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.