Skip to content

Releases: benvinegar/counterscale

v3.0.0-beta.1

21 Feb 04:22
Compare
Choose a tag to compare

Changes:

  • New CLI installer (npx @counterscale/cli install)
  • Deploys as a Cloudflare Worker again (no longer uses Cloudflare Pages)
  • Uses pnpm package manager for development

Note this is a major version change. You may need to make some changes if upgrading from a prior version.

Upgrading from v2.x

The biggest change here is that v2.x deployed Counterscale as a Cloudflare Pages project, whereas v3.x deploys it as a Cloudflare Worker.

First, run the installer and follow the prompts:

npx @counterscale/cli@latest install

Deploying will create a new Worker named counterscale (previously this was a Cloudflare Pages project also named counterscale). The deployment URL will have the form *-counterscale.your-subdomain.workers.dev.

Tracking Scripts

⚠️ You will need to update your tracking script(s) to point to this new URL. The installer will emit sample code that illustrates how to use the new URL.

Your historical data will stay unchanged.

Custom Domains

If you have a custom domain, you will need to delete that domain from the now-deprecated Cloudflare Pages project, and add it to the newly created Worker project.

Upgrading from v1.x

Since v1.x also deployed as a Cloudflare Worker, upgrading should be trivial. Just run the new CLI installer and follow the prompts:

npx @counterscale/cli@latest install

It should emit the same URL as before.

v2.5.1

24 Jan 14:52
Compare
Choose a tag to compare

Changes:

  • Fixes a major bug where bounce rate data wasn't being collected (#148)
    • If you are running v2.5.0, you are strongly encouraged to upgrade.

v2.5.0

16 Jan 20:54
Compare
Choose a tag to compare

Changes:

  • /collect endpoint now responds with Access-Control-Allow: * header (e2558aa)
  • Tracker now makes HTTP request to /collect using XMLHttpRequest POST (#143)
  • Can install tracker script as a TypeScript/JavaScript module (#143)
    • See README for instructions / API
  • Migrates to React Router 7 from Remix (#146)

v2.5.0-beta.3

15 Jan 19:17
Compare
Choose a tag to compare

Changes:

  • /collect endpoint now responds with Access-Control-Allow: * header (e2558aa)
  • Tracker now makes HTTP request to /collect using XMLHttpRequest POST (#143)
  • Can install tracker script as a TypeScript/JavaScript module (#143)
    • See README for instructions / API

v2.4.0

08 Jan 14:22
Compare
Choose a tag to compare

Changes:

  • Adds browser version tracking (#135)
  • Tracker now auto-instruments browser History API (#140)
  • Tracker now typed in TypeScript, tested with Playwright, and built with Vite (#132)
  • Project is now built, deployed, etc. using Turborepo (#132)

v2.3.0

20 Dec 14:26
Compare
Choose a tag to compare

Changes:

  • Upgrades Remix to 2.15.1 and opts into all future flags (#130)
  • Updates dependencies to remove high-sev vulnerabilities reported by npm audit (#131)

v2.2.2

19 Dec 18:39
Compare
Choose a tag to compare

Changes:

  • Fixes broken Admin URL in navbar (#129)

v2.2.1

14 Dec 14:50
Compare
Choose a tag to compare

Changes:

  • Fixed crash caused by bad SQL query when no results during a given period (#126)

v2.2.0

13 Dec 21:39
Compare
Choose a tag to compare

Changes:

  • Now collects and reports on Bounce Rate (#116)
  • Time series chart now renders 3 time series: visitors, views, and bounce rate. (#124)
  • Improved time series chart visuals including hover tooltip (#125)
  • Fixes bug where pagination on Path and Referrer cards where pagination wasn't functioning correctly. (#123)
  • Fixed bug where tailwind.config.js would not resolve modules in newer versions of Node (53d5835)

NOTE: Counterscale needs to start collecting bounce data before it can determine a bounce rate. If it does not have full bounce data for the current period, it will show "n/a".

v2.1.0

21 Nov 19:09
Compare
Choose a tag to compare

Changes:

  • Now supports "Yesterday" time range (#98)
  • Clearer error messages when CF_ACCOUNT_ID or CF_BEARER_TOKEN is not configured (#113)
  • Fixed bugs caused by inaccurate server-detected timezone (#109, #107)
  • Fixed bug where recent DST switchover caused inaccurate timeseries graph (#108)