feat(monitoring): single-source PostHog Error Tracking (drop Sentry)

[PierreBrisorgueil]

Summary

• Delete src/lib/plugins/sentry.js + src/lib/plugins/tests/sentry.unit.tests.js — Sentry plugin fully removed
• Drop @sentry/vue from package.json; lockfile regenerated
• Simplify src/lib/helpers/errorTracker.js — drop Sentry fan-out branch, PostHog-only path via $exception events remains (gated on analytics.posthog.errorTracking === true)
• Unregister Sentry from src/lib/plugins/index.js and src/main.js
• Config: src/config/defaults/development.config.js — drop analytics.sentry section, flip analytics.posthog.errorTracking default to true; src/config/index.js regenerated via generateConfig
• Tests: errorTracker.unit.tests.js updated (Sentry fan-out tests removed, PostHog path + failure isolation + non-Error normalization kept); plugins/tests/index.unit.tests.js updated (sentry removed from expected plugins list)

Rationale

PostHog Error Tracking GA supports full stack traces + source maps via @posthog/cli, native session-replay link (→ debug Vue UX bugs in 1 click), and free 100k exceptions/mo — sufficient for pre-PMF scale. Maintaining dual Sentry + PostHog adds +1 SaaS account, +1 SDK, +1 K8s secret, +1 CI sourcemaps step, and cross-tool funnel joins for no material gain at current scale. Sentry re-entry triggers: >100k exceptions/mo, distributed tracing need, or 24/7 oncall team.

Wave 2 downstream note (for /update-project sub-agent briefing)

Downstream projects that previously deep-merged analytics.sentry from devkit defaults will retain the stale shadow key after npm run update-stack, because deepMerge cannot remove keys — only override with null. Each downstream *.config.js that has a local analytics section must add:

analytics: {
  sentry: null,  // clean devkit shadow — sentry removed upstream
  posthog: { ... },
}

See feedback_config_deepmerge.md. Projects to check: trawl_vue, comes_vue, pierreb_vue, montaine_vue, ism_vue.

Test plan

• npm run lint — ESLint no issues
• npm run test:unit — 1592/1592 tests pass (99 test files)
• npm run test:coverage — 98.92% statements, 93.24% branches, no threshold violations
• CI green (ARC self-hosted runners)
• CodeRabbit review

Summary by CodeRabbit

• Chores
  • Removed error tracking dependency and consolidated error tracking to a single provider.
  • Updated error tracking configuration to use PostHog exclusively in development environments.

[coderabbitai]

Warning

Rate limit exceeded

@PierreBrisorgueil has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 54 minutes and 7 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 19eea2b5-690f-42c4-800d-425f9a71f0c5

📥 Commits

Reviewing files that changed from the base of the PR and between 4626732 and 88b2656.

📒 Files selected for processing (2)

• src/lib/helpers/errorTracker.js
• src/lib/plugins/tests/index.unit.tests.js

Walkthrough

This PR removes Sentry error tracking integration entirely and consolidates error tracking to PostHog only. Changes span dependencies, configuration, core implementation, plugin infrastructure, app initialization, and test coverage. All Sentry imports, configuration, plugin code, and registrations are eliminated.

Changes

Sentry Removal & PostHog Consolidation

Layer / File(s)	Summary
Dependency & Configuration package.json, src/config/defaults/development.config.js	@sentry/vue dependency is removed. PostHog errorTracking is enabled in development config, and example host URL updated to EU instance.
Error Tracking Implementation src/lib/helpers/errorTracker.js	Sentry import removed. captureException logic simplified to PostHog only, gated on config.analytics.posthog.key and config.analytics.posthog.errorTracking === true. Captures via posthog.capture('$exception', ...) with silent error swallowing.
Plugin Infrastructure src/lib/plugins/index.js, src/lib/plugins/sentry.js	Sentry plugin import and export removed from plugin index. Entire Sentry plugin module deleted.
App Initialization src/main.js	Sentry plugin registration .use(plugins.sentry, { router: appRouter }) removed from app bootstrap. Error handler and window event listener documentation updated to reflect PostHog-only tracking.
Tests src/lib/helpers/tests/errorTracker.unit.tests.js, src/lib/plugins/tests/index.unit.tests.js, src/lib/plugins/tests/sentry.unit.tests.js	Sentry mocks and imports removed from errorTracker tests. Test cases for Sentry-only and dual-tracker scenarios removed; PostHog coverage retained and expanded. Plugin index test updated to exclude sentry from expected exports. Entire Sentry plugin test file deleted.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• pierreb-devkit/Vue#3788: Adds Sentry integration to the same files this PR removes it from (plugins, config, main.js, tests).
• pierreb-devkit/Vue#4012: Implements dual Sentry and PostHog error tracking in the same error tracking surface (errorTracker.js, plugins, main.js, config).

Suggested labels

Feat

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main objective: removing Sentry and consolidating to PostHog Error Tracking.
Description check	✅ Passed	The description covers required sections (Summary, Rationale, Test plan) with substantial detail; missing Scope and Guardrails sections from the template, but overall comprehensive.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch posthog-single-source

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.54%. Comparing base (5f8b539) to head (88b2656).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4118      +/-   ##
==========================================
- Coverage   99.54%   99.54%   -0.01%     
==========================================
  Files          32       31       -1     
  Lines        1105     1089      -16     
  Branches      311      302       -9     
==========================================
- Hits         1100     1084      -16     
  Misses          5        5              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/lib/helpers/errorTracker.js`:
- Around line 19-20: Update the JSDoc for the PostHog error tracker to reflect
the actual enablement logic: say it is active when config.analytics.posthog.key
is set AND config.analytics.posthog.errorTracking is either the boolean true or
the string 'true' (matching the runtime check in errorTracker.js); reference the
config keys config.analytics.posthog.key and
config.analytics.posthog.errorTracking in the comment and remove the incorrect
assertion that only boolean true enables it.

In `@src/lib/plugins/tests/index.unit.tests.js`:
- Line 10: Test's expectedPlugins array is missing the i18n entry, so update the
unit test that defines expectedPlugins (the const expectedPlugins = [...] in
src/lib/plugins/tests/index.unit.tests.js) to include 'i18n' alongside the other
plugin names; this ensures the export contract asserted by the test matches what
src/main.js consumes (plugins.i18n) and prevents runtime failures.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: c0ab7976-2d8c-425d-b6b7-afdd3f27bb5a

📥 Commits

Reviewing files that changed from the base of the PR and between a582430 and 4626732.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (9)

• package.json
• src/config/defaults/development.config.js
• src/lib/helpers/errorTracker.js
• src/lib/helpers/tests/errorTracker.unit.tests.js
• src/lib/plugins/index.js
• src/lib/plugins/sentry.js
• src/lib/plugins/tests/index.unit.tests.js
• src/lib/plugins/tests/sentry.unit.tests.js
• src/main.js

💤 Files with no reviewable changes (4)

• package.json
• src/lib/plugins/index.js
• src/lib/plugins/tests/sentry.unit.tests.js
• src/lib/plugins/sentry.js

[Copilot]

Pull request overview

Removes the Sentry integration and consolidates client-side exception capture into a PostHog Error Tracking–only path (via $exception events), aligning the monitoring stack with PostHog as the single source of truth.

Changes:

• Removed Sentry plugin + tests, unregistered the plugin, and dropped @sentry/vue from dependencies.
• Simplified captureException to PostHog-only behavior (still gated by analytics.posthog.errorTracking === true / 'true').
• Updated configs/tests to reflect the PostHog-only capture path and enabled PostHog error tracking by default in development config (while still requiring a key to actually send).

Reviewed changes

Copilot reviewed 9 out of 10 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/main.js	Removes Sentry plugin registration and keeps global error handlers wired to captureException (PostHog-only).
src/lib/plugins/tests/sentry.unit.tests.js	Deletes Sentry plugin unit tests.
src/lib/plugins/tests/index.unit.tests.js	Removes sentry from the expected plugin export list.
src/lib/plugins/sentry.js	Deletes the Sentry Vue plugin implementation.
src/lib/plugins/index.js	Stops exporting the removed Sentry plugin.
src/lib/helpers/tests/errorTracker.unit.tests.js	Removes Sentry fan-out tests; keeps PostHog path + failure isolation + normalization coverage.
src/lib/helpers/errorTracker.js	Removes Sentry fan-out and documents PostHog-only exception capture behavior.
src/config/defaults/development.config.js	Removes analytics.sentry defaults and enables PostHog error tracking by default (still gated by key).
package.json	Drops @sentry/vue dependency.
package-lock.json	Regenerates lockfile to remove Sentry packages.

[PierreBrisorgueil]

Fixed in follow-up commit — JSDoc now correctly states 'true or "true"' to match isEnabled() semantics.

[PierreBrisorgueil]

Fixed — @PARAM type updated to {unknown} with a normalization note for callers and tooling.

All 4 actionable comments addressed in follow-up commit (JSDoc corrections + i18n added to plugin contract test).