Errors
Capture errors
You don't need Sentry. One line in your page or a small server-side module is enough.
Create a project
In « Paramètres, Connecteurs » (Settings, Connectors), create an Oxvel project. You get a key that starts with ox_. It can only send errors, so it can safely stay in your app's code.
In the browser
Add this line to the <head> of your page.
<script src="https://oxvel.dev/oxvel.js" data-key="ox_…" data-release="DEPLOYED_COMMIT"></script>
Uncaught errors and rejected promises are sent with the stack trace, the page and the latest events. Put the deployed commit in data-release, the uses it. The other options are in the .
Server side (Node)
Paste this module where your server starts. In a catch, call report(err).
const OXVEL = "https://oxvel.dev/api/ingest/ox_…"
export const report = (err) =>
fetch(OXVEL, {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
type: err?.name, message: err?.message ?? String(err), stack: err?.stack,
platform: "node", runtime: process.version,
release: process.env.VERCEL_GIT_COMMIT_SHA, environment: process.env.NODE_ENV,
}),
}).catch(() => {})
process.on("uncaughtException", (e) => report(e).finally(() => process.exit(1)))
process.on("unhandledRejection", (e) => report(e))Install in one click
The « Installer dans mon dépôt » (Install in my repository) button opens a draft PR that adds the capture in the right place. The « Tester » (Test) button sends a fake error to check that everything works.
How errors are grouped
The same error coming back 100 times gives a single incident, with a counter. Two errors are the same when they have the same type and start from the same place in your code (file and function). Without a stack trace, Oxvel compares the message, ignoring numbers and identifiers. Each new error gets a short identifier, such as MONAPP-12.