The double rendering of lifecycle methods in Strict Mode needs to be presented more loudly

I have just lost a day's work wondering why my GSAP animations weren't working only to realize the double call in strict mode. While I understand the reasons for strict mode, I still think having a Caveats section or something to warn developers would be highly beneficial.

I did stumble on this GSAP thread and it seems like both sides are just saying "It's not really my problem" while we the developers kind of suffer.

Now, I do know of the existence of the changelog but new developers wouldn't be aware of this issue right away and I just want to save their time. So, maybe having a Gotchas section where you can just write some notes regarding how strict mode calling twice may affects 3rd party libraries like GSAP's from() tweens could help developers tackle this issue early? Just my two cents.

首先定位现有的 Strict Mode 文档，并查看其中如何呈现其注意事项和 changelog。添加一条醒目的警告，说明生命周期方法会渲染两次，以及这对 GSAP 等第三方库的影响；当新开发者无需搜索 changelog 就能找到这些指南时，即可完成。