10 Commits

Author	SHA1	Message	Date
Austaras	bb02cdd26e	refactor(es/minifier): Simplify analyzer context (#8164)	2023-10-27 18:16:00 +00:00
Austaras	4f67794223	feat(es/minifier): Inline into the arguments of new using seq inliner (#8127)	2023-10-18 03:07:14 +00:00
Austaras	ff1ad95b59	feat(es/minifier): Compress common sub expressions in sequences (#7587)	2023-07-04 05:47:37 +00:00
David Sherret	064bcf4854	fix(es/codegen): Remove extra spaces in AssignPatProp and KeyValuePatProp (#7488) ... Co-authored-by: Donny/강동윤 <kdy1997.dev@gmail.com>	2023-06-07 05:08:35 +00:00
Austaras	5dbbbea2ef	fix(es/minifier): Mark all function params as potential property mutation (#7409) ... **Description:** This issue is more severe than I originally thought. It raises not in array indexing, but in function calls and property mutation. We should treat all function arguments as potentially be property mutated, otherwise following example ```js class A { a = 1 toString() { return this.a } } const a = new A() function foo(x) { x.a++ } const b = a + 1 foo(a) console.log(b) ``` would be error(It should log 2, but logs 3 after compress). As the result, massive regressions is unavoidable, since some of these optimizations may indeed cause error. Part of them can be mitigated with following optimization -- allow inline of ident even if its original value is mutated. Consider ```js export function foo(x) { const y = x x.a = 1 y.b = 2 } ``` If x is a primitive value, all mutations to its properties are ignored; if x is a object, then y refers to the same object no matter what mutation is performed. And there's still room for more, currently following code ```js export function foo(x) { const y = Math.floor(x); g(y); } ``` But I'd rather do it in a separate PR. **Related issue:** - Closes #7402.	2023-05-18 01:19:17 +00:00
Donny/강동윤	21e14787c5	fix(es/minifier): Don't inline into await from sequential inliner (#6839) ... **Related issue:** - Closes https://github.com/swc-project/swc/issues/6837.	2023-01-20 08:50:51 +00:00
Austaras	1cd7f617f9	feat(es/minifier): Inline a lazily initialized var if it's used once (#6237)	2022-10-26 06:02:22 +00:00
Austaras	657e5b3111	feat(es/minifier): Inline more lazily initialized vars (#6089)	2022-10-10 09:53:50 +09:00
Austaras	c4850997a2	feat(es/minifier): Inline vars initialized before the declaration (#6027)	2022-10-03 08:58:38 +00:00
Donny/강동윤	2ee3ad0066	fix(es/minifier): Don't inline into nested scope (#6002) ... **Related issue:** - https://github.com/vercel/next.js/discussions/30237#discussioncomment-3768734	2022-09-30 08:53:20 +00:00