Describe the bug

Type stripping has an edge case where it can have the wrong output when there is a return followed by a type with a newline, because of the no-lineterminator-here restriction after return.

Input code

function f() {
	return <T>
		(x: T)=>x;
}

Config

{
  "jsc": {
    "parser": {
      "syntax": "ecmascript",
      "jsx": false
    },
    "target": "es5",
    "loose": false,
    "minify": {
      "compress": false,
      "mangle": false
    }
  },
  "module": {
    "type": "es6"
  },
  "minify": false,
  "isModule": true
}

Playground link (or link to the minimal reproduction)

https://play.swc.rs/?version=1.7.1&code=H4sIAAAAAAAAA0srzUsuyczPU0jT0FSo5uIsSi0pLcpTsAmx4%2BLk1KiwUgjRtLWrsOaq5QIAdBqy7yoAAAA%3D&config=H4sIAAAAAAAAA1WPSw7DIAwF9zkF8rrbdtE79BAWdSIifrKJVBTl7iUE0maH3xsz8jooBbNoeKq1PMsQkYX4nEsi2Sf8lARIOxTNJia49XaWvRrRCtVoOxpIyBOluiX3hoMNQajjLXPGmzH%2FC3VwkUnkCu4o%2BsnSVTc0JbjwXmrZDkk50qF%2FwA%2FqsvNjMPLqm4kXGrYvhlQioBQBAAA%3D&strip-types=

SWC Info output

No response

Expected behavior

The output should have the same semantics as the input. The easiest way to get this would be to add in 0, after the return as in

function f() {
	return  0,
		(x   )=>x;
}

or to move the initial parenthesis as in

function f() {
	return  (
		x   )=>x;
}

Actual behavior

Because of the newline, the return is treated as having no operator.

Version

1.7.1

Additional context

Issue comes from node: nodejs/node#56597 (comment)

Note that the same bug occurs with throw instead of return. It probably would also occur for yield but that doesn't parse at all.