(12.0.0, SWC) TypeScript generics in objects incorrectly parsed as JSX

What version of Next.js are you using?

12.0.0

What version of Node.js are you using?

14.18.1

What browser are you using?

Chrome

What operating system are you using?

Linux

How are you deploying your application?

Vercel

Describe the Bug

Using the new SWC minifier on Next 12, objects that have functions with TypeScript generics seem to incorrectly be parsed as JSX.

Expected Behavior

TypeScript generics in objects with functions as keys should be correctly parsed

To Reproduce

Given the following code

export const Client = {
  axios: Axios.create({ baseURL: "..." }),
  delete<T extends Object>(params: T) {
    return Client.axios.request(params);
  },
}

Results in the following error:

Error: error: Expected a semicolon
   
    |
162 |   delete<T extends Object>(
    |         ^

error: Expected ',', got '< (jsx tag start)'
   
    |
162 |   delete<T extends Object>(
    |         ^

Caused by:
    0: failed to process js file
    1: Syntax Error

However, the following works OK

export const Client = {
  delete: function<T extends Object>(params: T) {
    return Client.axios.request(params);
  },
}

[ThewBear]

I have a .ts file with angle-bracket syntax type assertion and getting the Expected jsx identifier error in Next.js 12.0.1. It was working fine in Next.js 11. It should only give this error only in .tsx file.

[Derush]

You can us "as comst " instead of " <const> " your project code