Explore a compile-time step to add hooks

[btford]

I'm mostly just brainstorming/documenting this idea. I'm not sure if it's worth taking a shot at implementing it.

Suggested by @mikeal over here.

Pros:

• might be a smaller code size
• might be faster since you can unwrap/inline hooks

Cons:

• can't call any code that you didn't compile – you can't include jquery.js; you'd have to preprocess it first.
• perhaps harder to implement than patching (probably can't use static analysis) – ['setTimeout'].forEach(function (fn) { ... }};

[mikeal]

FTR, the tradeoffs probably aren't worth it. I was just thinking about the advantages/disadvantages of the two approaches.

[btford]

that's my feeling too, but I think it'd be a fun exercise

[AndrewKushnir]

This was implemented for the ngOnChanges lifecycle hook to provide better tree-shaking, see ng_onchanges_feature.ts.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}