Skip to content

Connect Solid on Vite

Set Solid on Vite up with one pull request Xovris opens for you.

Connect GitHub

Terminal window
npx xovris@latest init
Watch the first event arrive

Will it fit your project?

Checks a package.json fits – in your browser, sent nowhere.

Checked right here, by the same rules the set-up command uses. Nothing is sent anywhere.

    Run the wizard

    Xovris sets Solid on Vite up for you: connect GitHub once and Xovris raises one pull request that installs the SDK and writes the configuration, for you to review and merge – then it shows the first event the moment it arrives. Do it yourself instead: run one command in your Solid on Vite project – it signs you in through your browser, installs the SDK, writes the configuration and proves the first event arrived, and you never copy a key.

    Xovris makes this change for you: connect GitHub once and Xovris raises a pull request that lists every change, for you to review and merge.

    Connect GitHub

    What the wizard changes

    Before writing anything the wizard shows each change. It records every change in a manifest, so removal is exact.

    The wizard loads Xovris first in the entry your index.html starts; Solid on Vite is released once its install test passes in CI on the latest Vite and the package is published.

    This set-up works on npm, pnpm, yarn and bun, as of 14 November 2026.

    1. Detects Solid on Vite and your package manager
    2. Opens your browser to sign you in – no key to paste
    3. Installs @xovris/browser
    4. Writes to .env.local VITE_XOVRIS_INGEST_URL, VITE_XOVRIS_INGEST_KEY
    5. Waits until your first event is stored, then says so
    6. Records every change, so this takes it all out again: npx xovris@latest remove

    Variables it writes

    The wizard writes these to .env.local and adds that file to .gitignore if it is not already ignored. It refuses to write a key into a file git tracks.

    VariablePurpose
    VITE_XOVRIS_INGEST_URLWhere events are sent
    VITE_XOVRIS_INGEST_KEYThe ingestion key for this project (write-only: it can send events, never read them)

    If you already use another tool

    The wizard looks for existing instrumentation first and tells you what it will do before it changes anything, so you never send each error twice.

    FoundWhat the wizard does
    OpenTelemetryAdds Xovris as a second OpenTelemetry exporter – your existing setup keeps working unchanged.
    SentryOffers to run both side by side for a while, or to switch over; it never sends one error to Xovris twice.
    Datadog and New RelicLeaves the existing agent in place and offers to export through OpenTelemetry instead of adding a second agent.

    Check it works

    The wizard ends by waiting for your first stored event. To check again later, run:

    Terminal window
    npx xovris@latest verify

    Remove it

    This puts back every change the setup made and switches its key off, then confirms both:

    Terminal window
    npx xovris@latest remove

    What you get

    SignalState
    Server errorsNot collected
    Browser errorsIncluded
    TracesThrough OpenTelemetry
    MetricsNot collected
    LogsNot collected
    ReleasesIncluded
    Readable stack tracesIncluded

    Supported versions

    Written for Solid on Vite 6 or later (before 9), on Node.js 20.19 or later.

    Frameworkvite >=6.0.0 <9
    RuntimeNode.js >=20.19
    Package managersnpm, pnpm, yarn, bun
    Packagesnpm install @xovris/browser

    Ask Xovris

    Open the full page

    Your data is never used to train our AI. How your data is kept

    A problem is called fixed only once it works again. How each fix is checked

    XOVRIS LTD, registered in England and Wales, company number 17499910. Registered office: 66 Paul Street, London EC2A 4NA.