Repository navigation
Functions, when exported later, then called, are unnecessairly inlined #1328
Description
Given the following:
function a() {
return {
some: "data"
};
}
export const b = a()
export const c = a;Terser will output the following code:
function a(){return{some:"data"}}export const b={some:"data"};export const c=a;Expected:
function a(){return{some:"data"}}export const b=a();export const c=a;
Activity
tristan-f-r commentedon Dec 30, 2022
[-]Functions when exported later, then called, are unnecessairly inlined[/-][+]Functions, when exported later, then called, are unnecessairly inlined[/+]fabiosantoscode commentedon Jan 2, 2023
Interesting!
This is a consequence of dead code elimination being 2-step: inline, then remove.
If those 2 steps don't agree (inline thinks t() will be removed), it can cause duplicate code sometimes.
fix(javascript): keep minified output from growing where inlining or …