Changelog
Pick your platform, see only its install steps
- Install
- Developers
import { Highseat } from "highseat/next"export default function RootLayout({ children }: { children: React.ReactNode }) { return ( <html lang="en"> <body> {children} <Highseat site="YOUR_SITE_ID" /> </body> </html> )}
Adding a site now starts with one question: what is the site built on? Pick from ten platforms, or Any other site, and Highseat shows only the steps for that one.
Ten platforms, three groups
The picker sorts platforms by how the site is built. Website builders such as Webflow, Framer, Squarespace, Wix, Shopify and WordPress take one tag in their header settings or theme. Next.js, React and TanStack Start install the package, and Astro takes a script tag in its layout. Any other site covers the rest, and typing a name filters the list.
One package for frameworks
Next.js, React and TanStack Start sites install highseat and render <Highseat /> once, in the root layout. The package loads the tracker from Highseat or from your own proxy path. A call made before the tracker loads waits for it, and no call ever throws.
npm install highseatThe same code everywhere
Onboarding, Installation settings and highseat.com/skill.md read every snippet from one source, so a coding agent follows the same steps you see. A test fails when the dashboard shows code the package README does not.
Improvements
- Installation settings show when the first pageview arrived and when the proxy last sent an event.
- highseat.com/skill.md gives a coding agent the same install steps to follow.
Fixes
- Deleting a site or a user now removes every stored event. A failed erasure can be retried.
- Bot traffic reclassified after the fact no longer counts toward a plan's events.