Parser error when using TypeScript 4.7 Instantiation Expressions

[OliverJAsh]

Your Environment

• Prettier version: 2.7.0
• node version: 16.3.0
• package manager: yarn@1.22.17
• IDE: N/A

Describe the bug

Parser error when using TypeScript 4.7 Instantiation Expressions (supported in Prettier 2.7.0).

To Reproduce

Using the latest version of prettier and @trivago/prettier-plugin-sort-imports at the time of writing:

package.json:

{
  "dependencies": {
    "@trivago/prettier-plugin-sort-imports": "^3.2.0",
    "prettier": "^2.7.0"
  }
}

file.ts:

interface Box<T> {
  value: T;
}
function makeBox<T>(value: T) {
  return { value };
}
const makeHammerBox = makeBox<Hammer>;
const makeWrenchBox = makeBox<Wrench>;

$ prettier --parser typescript file.ts
file.ts[error] file.ts: SyntaxError: Unexpected token (7:37)
[error]   1 | interface Box<T> {
[error]   2 |   value: T;
[error]   3 | }
[error]   4 | function makeBox<T>(value: T) {
[error]   5 |   return { value };
[error]   6 | }
[error]   7 | const makeHammerBox = makeBox<Hammer>;
[error]   8 | const makeWrenchBox = makeBox<Wrench>;

Expected behavior

No error

---

The error only occurs when @trivago/prettier-plugin-sort-imports is installed—if remove uninstall it, the parser issue disappears. To make issues like this easier to debug in the future, I would suggest improving the error output so to make it clearer that this error originates from the parser inside of @trivago/prettier-plugin-sort-imports and not the parser inside of prettier.

[OliverJAsh]

Workaround (via #141):

package.json:

  "resolutions": {
    "@trivago/prettier-plugin-sort-imports/**/@babel/parser": "7.18.5"
  }

[odiak]

I made pull request for this: #161.

[OliverJAsh]

I just encountered the same issue trying to use TypeScript 4.9's satisifies operator.

[taiwabisabi]

Same as @OliverJAsh with TypeScript 4.9's and satisifies operator.

[taiwabisabi]

I've just submitted a pull request to update prettier to 2.8 to handle new implementation of TS 4.9 version such as satisifies operator.
-> #194

[OliverJAsh]

I think the best way to solve this issue would be by solving #141.

[byara]

The issue should be resolved in v4.1.0.

[OliverJAsh]

I think the best way to solve this issue would be by solving #141.

@byara Do you have any thoughts on this? I fear it's only a matter of time before this issue happens again, so I was hoping we could find a more permanent fix.