chg: re-initialize analytics

[synoet]

No description provided.

[coderabbitai]

Walkthrough

The createAnalytics factory function has been modified to invoke initializeProviders() immediately upon its definition. This change shifts the timing of provider initialization from lazy loading on first track/identify call to eager initialization during analytics construction. The modification adds two lines and preserves existing guard conditions and provider initialization logic.

Poem

🐰 Early morning, providers wake,
No more waiting for first track,
Analytics ready from the start,
Swift and steady, right on track! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided by the author, making it impossible to evaluate whether the description relates to the changeset.	Add a description explaining why analytics providers need to be re-initialized earlier in the construction flow and any implications of this timing change.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 're-initialize analytics' is clearly related to the main change, which moves analytics provider initialization from on-demand to immediate initialization during construction.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch synoet/initialize-analytics

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Preview: https://synoet-initialize-analytics-z9q72s.preview.macro.com/app (6e9e9e8)

[dev-rb]

My bad

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@js/app/packages/app/lib/analytics/analytics.ts`:
- Around line 60-61: The current eager call to initializeProviders() during
construction can permanently leave analytics uninitialized because tryInitialize
swallows errors; change the pattern so initializeProviders() is idempotent and
only marks initialization as complete on success, and modify track(...) and
identify(...) to call initializeProviders()/tryInitialize() on each use if not
yet successfully initialized (retry-on-use) instead of assuming init ran once;
ensure tryInitialize returns/propagates failure state (or a boolean) and that
any initialization flag (e.g., isInitialized) is set only after successful
provider setup so transient errors do not disable future attempts.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 153c1c5c-10a8-4a96-82e1-4eea8421e537

📥 Commits

Reviewing files that changed from the base of the PR and between 9118029 and a8a9caa.

📒 Files selected for processing (1)

• js/app/packages/app/lib/analytics/analytics.ts