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.

Commencez par localiser la documentation existante de Strict Mode et par examiner comment ses limites et son changelog sont présentés. Ajoutez un avertissement bien visible indiquant que les méthodes du cycle de vie sont rendues deux fois, ainsi que l’impact sur les bibliothèques tierces telles que GSAP ; le travail sera terminé lorsque les nouveaux développeurs pourront trouver ces informations sans rechercher dans le changelog.