BUG REPORT · VUE

Bug Report for Vue

Bug reports with severity, environment, and reproduction steps. Free for 500 submissions per month — no backend, no SDK, no plugin.

Get free access key Copy the code

500/mo free·no card·drop-in for Vue

form.htmlhtml28 lines

01<form action="https://splitforms.com/api/submit" method="POST">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
03  <input type="hidden" name="subject" value="New bug report">
04 
05  <label for="title">Short summary *</label>
06  <input id="title" type="text" name="title" placeholder="What went wrong?" required>
07  <label for="severity">Severity *</label>
08  <select id="severity" name="severity" required>
09    <option value="">Choose…</option>
10    <option>Critical</option>
11    <option>High</option>
12    <option>Medium</option>
13    <option>Low</option>
14  </select>
15  <label for="browser">Browser &amp; OS</label>
16  <input id="browser" type="text" name="browser" placeholder="Chrome 120 / macOS">
17  <label for="steps">Steps to reproduce *</label>
18  <textarea id="steps" name="steps" placeholder="1. Go to…
192. Click…
203. See error" required></textarea>
21  <label for="email">Your email (so we can follow up) *</label>
22  <input id="email" type="email" name="email" placeholder="you@example.com" required>
23 
24  <!-- honeypot — bots fill every field -->
25  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
26 
27  <button type="submit">Send</button>
28</form>

500

submissions / mo, free

fields, ready to ship

code outputs

60s

from copy to inbox

§ 00Vue + Bug Reportplatform-specific integration guide

Why Vue developers choose splitforms for bug report

Vue's reactivity system is great for UI state but doesn't help with form delivery — you still need somewhere to POST the data. The bug report on this page uses Vue's <code>@submit.prevent</code> to intercept the form event, builds a <code>FormData</code> object, and fires a <code>fetch</code> POST to splitforms. Works identically in Vue 2 (Options API) and Vue 3 (Composition API with <code>ref</code>). Because it's just a standard POST, it works with Nuxt, Vite, and any Vue bundler without a custom plugin or module.

§ 00Quick answerHTML · support

Yes — this is the shortest safe path for Vue.

Use the HTML snippet on this page, keep the bug report fields visible in your Vue UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.

best implementation

Paste the HTML version, then replace YOUR_ACCESS_KEY.

The posted payload contains short summary, severity, browser & os, steps to reproduce, your email (so we can follow up). Required fields are short summary, severity, steps to reproduce and your email (so we can follow up).

native vue reality

Vue ships nothing form-related beyond v-model for two-way binding.

use case fit

User-reported bugs are signal — but only if the report has steps-to-reproduce and a screenshot. The form forces the structure, then files the issue automatically.

§ 01Bug Report × Vuewhy this combination, in 80 words

Built for Vue developers who hate operating a backend.

Splitforms is the form backend for Vue sites. One POST endpoint, no SDK, no plugin — drop the bug report into a page and ship.

Splitforms is the form backend for Vue sites. One POST endpoint, spam filtering, and a real dashboard — drop-in, no server, no PHP. Free for 500 dashboard submissions per month; Starter adds email, signed webhooks, exports, and retained uploads; Pro is $5/mo for 5,000.

✦ what you get on the free plan

✓500 form submissions per month
✓2 forms on Free; unlimited forms on Pro
✓Spam protection (honeypot + classifier)
✓Webhooks: Slack, Discord, WhatsApp, custom
✓CSV export of all submissions
✓Email notifications (CC and BCC on Pro)

§ 02Copy-paste codeHTML · 28 lines

Drop into any Vue project.

Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Vue page, and ship. No build-time integration required.

form.htmlhtml28 lines

01<form action="https://splitforms.com/api/submit" method="POST">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
03  <input type="hidden" name="subject" value="New bug report">
04 
05  <label for="title">Short summary *</label>
06  <input id="title" type="text" name="title" placeholder="What went wrong?" required>
07  <label for="severity">Severity *</label>
08  <select id="severity" name="severity" required>
09    <option value="">Choose…</option>
10    <option>Critical</option>
11    <option>High</option>
12    <option>Medium</option>
13    <option>Low</option>
14  </select>
15  <label for="browser">Browser &amp; OS</label>
16  <input id="browser" type="text" name="browser" placeholder="Chrome 120 / macOS">
17  <label for="steps">Steps to reproduce *</label>
18  <textarea id="steps" name="steps" placeholder="1. Go to…
192. Click…
203. See error" required></textarea>
21  <label for="email">Your email (so we can follow up) *</label>
22  <input id="email" type="email" name="email" placeholder="you@example.com" required>
23 
24  <!-- honeypot — bots fill every field -->
25  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
26 
27  <button type="submit">Send</button>
28</form>

§ 03Setup3 steps · 60 seconds · zero config

Generate, embed, receive.

Three actions stand between you and your first bug report submission. None of them require a backend, a database, or a CAPTCHA library.

STEP 01GENERATE

Generate a free splitforms key

Create your form

key=sk_live_••••••••

STEP 02EMBED

Paste the bug report into your Vue project

Drop the form snippet into a Vue page, component, or layout. Replace YOUR_ACCESS_KEY with the key from your dashboard. The form action is a hard-coded URL — no env vars or build-time wiring needed.

snippethtml

<form action="https://splitforms.com/api/submit" method="POST">
  …
</form>

STEP 03RECEIVE

Receive submissions

Dashboard updates live on Free. Starter adds email delivery, signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.

inbox · 1 newjust now

FROM contact@yoursite.com

New bug report

Maya Iyer maya@studio71.co

Loved the demo — quick question about pricing on the 3-year plan. Are usage limits per project or account-wide?

§ 03bBug Report Form (Issue Submission)template-specific playbook

The reason this bug report exists.

Screenshot upload (Pro) · webhooks into Linear / GitHub Issues / Slack.

why it matters

Bug reports without reproduction steps waste hours of triage. The form structures the report — what happened, what was expected, steps to reproduce, browser / OS / device, screenshot. Screenshot upload is critical: 'the page broke' tells you nothing; a screenshot of the broken state tells you everything. Webhook the structured report into Linear or GitHub Issues so it lands as a triageable ticket, not a Slack message that scrolls away. For SaaS teams the time saved is huge — instead of a 4-message back-and-forth gathering basic context, the engineer opens the issue and starts debugging.

route the submission

Structure the report

Required: what happened, what you expected, steps to reproduce. Optional: browser, OS, device, URL where it occurred. Most templates auto-detect browser/OS via JS so the user doesn't have to fill them.

Screenshot upload

Pro file upload — drag-and-drop a screenshot or screen recording. Multi-file accepted. Image attachments arrive on the email and via webhook with signed URLs.

Webhook into Linear / GitHub

Lands as a Linear issue or GitHub issue with the structured report as the body and the screenshot embedded. Engineer opens, reproduces, fixes — no triage thread needed.

§ 03cVue production notesnative path · deploy · gotchas

What changes when this bug report lives in Vue.

These notes come from the Vue platform registry and are rendered on this template page so crawlers see the framework-specific answer without opening a separate guide.

without splitforms

Vue ships nothing form-related beyond v-model for two-way binding. To deliver a submission anywhere, you write the same backend stack as React: an Express/Nitro/Hono route, an email provider, a database, spam filtering. Nuxt narrows the gap with /server/api routes, but you're still operating the route. Pinia/Vuex don't help — they're for client state, not network. The Vue ecosystem has FormKit and VeeValidate for validation UX, but neither delivers submissions. Splitforms slots in as the missing endpoint: any Vue 2 / Vue 3 / Nuxt setup posts a FormData to one URL, gets { success: true } back, done.

deploy notes

Vue + Vite produces a static bundle that deploys anywhere. For Nuxt, every Nitro preset (Vercel, Netlify, Node, Cloudflare, static, AWS Lambda) works identically because the form posts client-side. On Cloudflare Pages with the Nuxt Cloudflare preset, avoid proxying through /server/api — the fetch round-trip eats the 10ms CPU budget on the free tier; post directly to splitforms. Vite-only (non-Nuxt) projects must use VITE_SPLITFORMS_KEY or env vars are silently undefined client-side. Nuxt uses runtimeConfig.public.splitformsKey. Both inline the value into the bundle, so domain-lock the key in the splitforms dashboard.

Vue gotcha

ref() doesn't auto-unwrap inside a template handler

If you write status === 'loading' inside <script setup> it works because Vue auto-unwraps refs in templates — but inside a function you need status.value. Mixing the two is the #1 cause of "why isn't my button disabling?" bugs in Vue contact forms.

Vue gotcha

v-model and FormData read different sources

If you bind inputs with v-model="name" to a ref and then build new FormData(e.target), FormData reads the DOM — which Vue keeps in sync — so it works. But if you bind a computed value and the input doesn't have a name attribute, FormData drops it silently. Always set name="…" on every input.

Vue gotcha

@submit fires before .prevent unless you spell it right

Vue's event modifier syntax is @submit.prevent="onSubmit". People often write @submit="onSubmit" and then forget to call e.preventDefault() inside the handler — the page reloads and the fetch is cancelled mid-flight.

Vue gotcha

Vite env vars need the VITE_ prefix or they're undefined at build

Reading import.meta.env.SPLITFORMS_KEY returns undefined unless you rename it to VITE_SPLITFORMS_KEY (Vite) or expose it via runtimeConfig (Nuxt). Vite intentionally hides anything without the prefix to prevent leaking server secrets.

PATTERN A

Pattern A — `<script setup>` with status ref

Modern Vue 3 SFC, half the boilerplate of Options API, full reactivity. status is a single ref<'idle' | 'loading' | 'ok' | 'err'>. Use the same wiring for the bug report fields on this page.

pattern-a.txtvue17 lines

01<script setup>
02import { ref } from "vue";
03const status = ref("idle");
04async function onSubmit(e) {
05  status.value = "loading";
06  const fd = new FormData(e.target);
07  fd.append("access_key", import.meta.env.VITE_SPLITFORMS_KEY);
08  const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
09  status.value = (await r.json()).success ? "ok" : "err";
10}
11</script>
12<template>
13  <form @submit.prevent="onSubmit">
14    <input name="email" type="email" required />
15    <button :disabled="status === 'loading'">Send</button>
16  </form>
17</template>

PATTERN B

Pattern B — composable for reuse across forms

Wrap the splitforms POST in a useSplitforms() composable. Multiple forms (contact, newsletter, demo) share one implementation. Test once, ship everywhere. Use the same wiring for the bug report fields on this page.

pattern-b.txtvue14 lines

01// composables/useSplitforms.js
02import { ref } from "vue";
03export function useSplitforms() {
04  const status = ref("idle");
05  async function submit(formEl, formName) {
06    status.value = "loading";
07    const fd = new FormData(formEl);
08    fd.append("access_key", import.meta.env.VITE_SPLITFORMS_KEY);
09    fd.append("form-name", formName);
10    const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
11    status.value = (await r.json()).success ? "ok" : "err";
12  }
13  return { status, submit };
14}

§ 04Field-by-field rundown5 fields · names you POST

What every field actually does.

Each field below ships in the bug report template — rename, remove, or add your own. Splitforms accepts any name you POST.

titleREQUIRED

TEXT

Short summary

Buyer-persona signal — IC vs decision-maker changes the follow-up cadence.

placeholder · What went wrong?

severityREQUIRED

SELECT

Severity

Triage signal — drives whether this pages on-call or waits till Monday.

CriticalHighMediumLow

browser

TEXT

Browser & OS

Repro context for engineering — saves a back-and-forth.

placeholder · Chrome 120 / macOS

stepsREQUIRED

TEXTAREA

Steps to reproduce

Free-text input — no character limit, expands as the visitor types.

placeholder · 1. Go to… 2. Click… 3. See error

emailREQUIRED

Your email (so we can follow up)

Reply-to address — splitforms wires this so hitting reply goes back to the sender.

placeholder · you@example.com

§ 05Bug Report on other frameworks21 frameworks · same backend

One backend. Every framework.

The same bug report template works on every framework splitforms supports. Pick yours.

§ 06Questions9 answered

Bug Report on Vue — FAQ.

Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.

01Does this bug report work on Vue?

Yes. The form is plain HTML with a single POST endpoint, so it runs on any Vue site without server-side code, plugins, or SDKs. Drop the snippet into a Vue page or component and submissions land in your splitforms dashboard.

02How much does the bug report cost on Vue?

Free for 500 submissions per month — no credit card, no trial. Pro is $5/mo for 5,000 submissions, and there's a one-time $59 3-year plan (15,000 submissions/mo for 36 months). The same pricing applies regardless of which framework hosts the form.

03Can I customize the fields?

Yes. The template ships with sensible defaults (short summary, severity, browser & os, steps to reproduce…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.

04How does spam protection work on the bug report?

A hidden honeypot field catches dumb bots, and a tuned classifier scores the rest. You only see real submissions in your dashboard. No CAPTCHA, no friction for human users — and it works the same on Vue as on any other framework.

05Can I send the bug report submissions to Slack or Discord?

Yes. Webhooks are available on Starter and above, with auto-formatted payloads for Slack, Discord, and WhatsApp (via CallMeBot). Or send raw signed JSON to any URL — Zapier, n8n, your own server. Configure in the splitforms dashboard.

06Will it work on a static Vue site?

Yes — the form posts directly to splitforms from the browser, so no server is involved. Works on Vercel, Netlify, GitHub Pages, Cloudflare Pages, S3, or any plain Apache host.

07Should I auto-detect browser / OS?

Yes — JavaScript can read navigator.userAgent and pre-fill hidden fields with browser name, version, OS, and screen size. The user doesn't see them; the engineer gets them. Saves 90% of 'what browser are you on?' replies.

08Can I integrate with Linear / GitHub / Sentry?

Yes — webhook the JSON. Linear and GitHub both accept inbound issue creation via API or Zapier. Sentry doesn't accept user-reported bugs as events but you can webhook to a Slack channel where the on-call engineer triages and creates the Sentry issue manually.

09How do I prevent abuse / spam in bug reports?

Public bug-report forms attract spam — hidden honeypot plus splitforms' classifier catches most. Require an email field; bots filling random emails get filtered by the classifier. For severe abuse, gate the form behind a logged-in user session.

§ 07Comparisonvs Web3Forms · vs Formspree

splitforms vs everything else.

Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.

Feature	Web3Forms	Formspree	splitforms
Free monthly submissions	250	50	500
Custom fields beyond contact	Yes	Pro tier	Free
Webhooks (Slack / Discord)	Pro tier	Pro tier	Free, signed
AI / MCP submission inbox	No	No	Yes
Long-term plan (3-year flat)	—	—	$59 every 3 years

§ 08More templates for Vue5 adjacent patterns

Ship a bug report on Vue in 60 seconds.

500 submissions per month, free forever. No credit card. Copy the snippet above and paste it into your Vue project.

Get free access key →Read the docs

founders pricing locked in · early access open

Bug Report for Vue

Why Vue developers choose splitforms for bug report

Yes — this is the shortest safe path for Vue.

Paste the HTML version, then replace YOUR_ACCESS_KEY.

Built for Vue developers who hate operating a backend.

Drop into any Vue project.

Generate, embed, receive.

Generate a free splitforms key

Paste the bug report into your Vue project

Receive submissions

The reason this bug report exists.

Structure the report

Screenshot upload

Webhook into Linear / GitHub

What changes when this bug report lives in Vue.

ref() doesn't auto-unwrap inside a template handler

v-model and FormData read different sources

@submit fires before .prevent unless you spell it right

Vite env vars need the VITE_ prefix or they're undefined at build

Pattern A — `<script setup>` with status ref

Pattern B — composable for reuse across forms

What every field actually does.

Short summary

Severity

Browser & OS

Steps to reproduce

Your email (so we can follow up)

One backend. Every framework.

Bug Report on Vue — FAQ.

splitforms vs everything else.

Other ready-to-ship Vue forms.

Ship a bug report on Vue in 60 seconds.