CSV import SDK for React, Vue, Angular & plain HTML — self-hosted

A CSV import SDK should disappear into your app, not wrap it. Mildport’s SDK surface is deliberately boring: a standard custom element — usable from React, Angular, Vue, Svelte or plain HTML — plus a typed React wrapper. No iframe. No vendor runtime. No lock-in at the boundary.

The whole API model

<mildport-import
  api-base-url="https://imports.your-infra.example"
  license-key="SIGNED_TENANT_KEY"
></mildport-import>

• In: attributes/properties — target fields (targets or a server catalog key), host config, hooks for cleaning and results.
• Out: DOM events — import-applied with the mapped, validated rows (browser mode) or a signed webhook to your backend (production default).
• Types: shipped with the package; the React wrapper (@capitality-io/mildport-react) gives you props/events idiomatically.

React example:

import { ImportSuite, type AppliedDetail } from '@capitality-io/mildport-react';

<ImportSuite
  apiBaseUrl={API}
  licenseKey={key}
  targets={targets}
  onApplied={(d: AppliedDetail) => refresh(d)}
/>;

Per-framework snippets (HTML, React, Vue, Svelte, Angular): Frameworks.

Why “element, not SDK-platform” matters

Cloud importer SDKs are clients of the vendor’s service — your customer’s file rides through their cloud, and the “SDK” is a leash. The Mildport element is a client of your deployment: self-hosted engine, offline-verifying license, and an offline widget mode that needs no server at all — useful for demos, previews and air-gapped evaluation.

Need headless instead of a UI? The same engine exposes a REST API and an MCP surface — see CSV import API.

Next: Frameworks, Quickstart (~10 minutes), or try the playground first.