[Constant logs in console.]

The console debugger was logging animation events and putting into the console 😅

Mystery solved

[Constant logs in console.]

Okay, so after some further investigation I think it's limited to FireFox developer edition

Seems as though the logs only appear in that browser, not in Chrome or Safari. The logs specifically come from The _ticker function in gsap-core.js and more specifically this line is where FireFox flags the log output but clearly it's not a console.log.

 

You can see from a simple codepen it outputs a lot of logs whenever GSAP does its thing in Firefox Developer -

See the Pen mdPzJKp by GreenSock (@GreenSock) on CodePen

 

manual || (_id = _req(_tick)); //make sure the request is made before we dispatch the "tick" event so that timing is maintained. Otherwise, if processing the "tick" requires a bunch of time (like 15ms) and we're using a setTimeout() that's based on 16.7ms, it'd technically take 31.7ms between frames otherwise.

[Constant logs in console.]

In package.json gsap is registered as 3.10.4. You can also see from the ScreenShot ScrollTriggerand gsap-core are outputting logs

[Constant logs in console.]

Hi,

 

This is something I've noticed a lot recently, I'm unsure if it;s normal or I'm doing something incorrectly.

 

We make use of GSAP and ScrollTrigger throughout the site, and it's added to our JS via NPM/Import to the JS files.

When looking at the browser console we're constantly getting an integer and an undefined being output to console.log from gsap-core.js

It's making things a little annoying to debug and bloating up the log screen.

 

Does anyone have any idea why GSAP would be doing this?