Debug mode doesn't work about analytics-next HOT 5 CLOSED

Oh I see now, it's not that it wasn't being activated, it's just that all page and track calls had already been processed by the time that I had activated the debug mode and it's no longer being maintained between page refreshes.

This does make it rather tricky to debug page calls since they will inevitably have been processed by the time I can enable the debug mode on a page, but that's just a matter of ergonomics and not a bug as I assumed it was.

However, the case with the debug mode that won't turn off after updating to analytics-next does seem to be real.
This can be reproduced on segment.com by manually setting the relevant localstorage entry:

localStorage.setItem('debug', 'analytics:*')

If debug mode was enabled by the old analytics library this will still have been set, and analytics-next still seems to process this in some way.
The output is styled like the old debug mode, but it lacks the more detailed debug messages: (screenshot is from another site)

from analytics-next.

Hi @JeroenBakker, thanks for opening the issue.

Debug mode can be enabled by calling analytics.debug(true).

For the second point, I don't believe this should be an issue because the old analytics library keeps track of debug mode using localstorage, while analytics-next keeps track of it on the analytics object itself.

from analytics-next.

I've also tried using analytics.debug(true) and it didn't work for me.
I didn't mention it since the documention only says analytics.debug().

Are you saying that debug mode does work for you on segment.com, and that this issue is specific to me?

And I would have expected analytics-next to use something like localstorage to maintain the debug mode between page refreshes, the documentation still says to "Refresh the page after you invoke debug to see the messages"

from analytics-next.

Thanks for pointing out the documentation, I'll get that updated.

Debug mode does work for me on segment.com, here's an example (don't refresh):

from analytics-next.

Got it, thanks. Looks like our integrations are using the old debug method. I will push out a fix for disabling that.

As for the debugging page calls, I would recommend adding the debug call to the snippet if needed.

from analytics-next.