Segment broke with next js 13.5.2

[AbdelrhmanX7]

i got this issue while i am using yarn build with next js 13.5.2

[silesky]

Thanks for opening an issue @AbdelrhmanX7. We made some changes that I think likely surfaced this issue recently, but It does looks like you're calling .track in a server environment. This is a no/no, particularly as this library is not isomorphic.

From 1.58.0 onward, I think it's extra important that you ensure you only call analytics.track() in a browser environment so you don't get runtime errors.

For more info, check out these next.js examples:
https://github.com/vercel/next.js/tree/canary/examples/with-segment-analytics
https://github.com/vercel/next.js/tree/canary/examples/with-segment-analytics-pages-router

[AbdelrhmanX7]

I downgrade to segment v1.51 and everything works fine now and i am already using segment analytics.track in a client side and this issue just appeared from nothing and i don't even know what is the main reason for this issue everything was fine and suddenly everything stopped working

[silesky]

@AbdelrhmanX7

"document is not defined" means that it's being called in a server context. Please see those next.js examples I posted in my previous comment.

Older versions of this library may have seemed like they "worked" because this error didn't bubble up in your code, but calling track in a server context is never something we support, and can even be dangerous if it can result in fatal unhandled promises that could even crash future node app inadvertently. It's actually better to fail loudly.

Our position is basically that calling analytics methods in a server context represents a bug in one's code, so it's up to ths owner to fix it. Usually it's just following established patterns. e.g. call track in a useEffect hook, check for the existence of "window", etc. See Next.js examples.