fix(es/minifier): Use unsafe option for arrow => method

[kdy1]

Description:

Related issue:

• Closes swc minifier breaks hls.js #6504.
• Error in production version minification in next 13, error not in next 12 or dev version of next 13 vercel/next.js#43208.

---

Investigation

This is caused by arrows, and seems like a same issue as #6507

({foo(){}}).foo.toString()

prints foo(){}.

[kdy1]

swc-bump:

• swc_ecma_minifier

[jridgewell]

Does this really fix either bug? It seems like we're just avoiding it because we're not converting to method shorthand anymore, but the real bug is that the compresser is omitting the {} enclosing object?

[kdy1]

@jridgewell

{} not omitted by the compressor/codegen.
The problem is eval and .toString() of arrow functions.

({foo(){}}).foo.toString() prints 'foo(){}', and if it's used in eval, the problem occurs

[jridgewell]

Ok, crawling through the bugs it's being caused because they're doing string concatenation of functions, which is inherently buggy if we're minifying it.

[swc-bot]

Automated review comment generated by auto-rebase script