Get started
Changelog10 changes

The command line tool now finds events in real monorepos and in every part of a component's template

Added

  • The command line tool now finds tracking calls in projects where each app has its own TypeScript settings and shares code with other packages in the same repository, including when nothing has been installed yet.
  • Tracking calls are now found when a helper calls another helper, however many levels deep, and when the analytics library is loaded on demand or the helper comes back from a hook.
  • The Vue, Svelte, Astro and Angular plugins now read tracking calls anywhere in a component's template (handlers, interpolations, bindings and conditions), and the Astro plugin also reads the page's script tags.
  • Event names that start with a dollar sign, such as `$pageview`, are now found.
  • `eventra init` now enables the plugin for the framework it finds in your project when it is installed, and tells you what to install when it is not.

Changed

  • A new `eventra.json` made by `eventra init` now leaves out test files and coverage output, so events fired from tests no longer show up as features. Existing files keep scanning what they scanned.
  • Scanning commands now ask for more memory by themselves when a repository is large, instead of stopping with an out-of-memory error.

Fixed

  • The Angular plugin no longer prints errors for generated documentation pages that are not templates.
  • Projects whose main TypeScript settings only point at other settings files (the usual Vue and Vite layout) now resolve their aliased imports.
  • The Svelte plugin now finds tracking calls written directly in a component's markup, such as a click handler on a button. After the latest command line tool update these were no longer picked up.