No autoTrack in production

[tmlmt]

Hello ! Just installed nuxt-umami with basic config (id + host only) and things worked great in dev. Moving in production, I realize that there is no activity sent to Umami. Browsing the website doesn't lead to any realtime activity.

I double-checked id and host; the website builds without error; no error in the logs. So I suppose it should be in place as it should.

Is this an expected behavior with Nuxt in production (SSR)? Some kind of caching happening maybe? Shall I therefore use the tracking methods manually? Or might there be a bug somewhere? I'd appreciate help if debugging's needed.

[ijkml]

Hey 👋
Are you using Umami Cloud?

[ijkml]

Yeah, the debug function is turned off for production, an empty function is exported and anything that might break would do so silently (hence the empty function error).

nuxt-umami/internal/debug.ts

Lines 21 to 23 in 0e2dcae

	const helloDebugger = process.env.NODE_ENV === 'production'
	? (id: ErrorId, raw?: any) => {}
	: (id: ErrorId, raw?: any) => {

I'm not too sure I understand what you mean by "consequences of using extends", but I doubt module/layer should matter 😅.

[ijkml]

Anyway, glad it works for you now.

[tmlmt]

Yeah no sorry I don't know why I was expecting a more verbose (info-style) debugger but as everything was silent (because there was no error per se)...

[ijkml]

I understand, but I think analytics should be quiet and not noticeable.

Anyway, don't know if you noticed, but env vars are now supported directly. https://github.com/ijkml/nuxt-umami#environment-variables

[tmlmt]

Absolutely. And thanks for that 😊 I will continue exploring 🌍

[tmlmt]

v2.1.0 solved the issue. See other thread in that discussion :)

[ijkml]

Awesome!