Measured entry

kokonut-file-upload

inputdark-futuristicmotion on file

A client-side drag-and-drop file picker with animated idle, dragging, progress, cancel, and error states. It ships as a shadcn registry TypeScript component, uses Tailwind utility classes and a local cn helper, and depends on React, Motion, and Lucide. Its built-in progress is simulated, so real transfer logic belongs in the success callback or a replacement handler.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of kokonut-file-upload at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of kokonut-file-upload at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of kokonut-file-upload at 1440 pixels wide
Harness screenshot at 1440 pixels wide. No horizontal overflow recorded.

Measured

Every value below was written by the harness on the run that produced the frames above. None of it is derived from the prose.

Harness measurements recorded for kokonut-file-upload
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal72.7 KB (138.1 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

BARE BUILD

✗ Build failed in 1m 52s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/components/kokonutui/file-upload.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A credible, adaptable drop zone when the surrounding app owns the actual upload. It builds and mounts cleanly in the prepared harness, but it needs a shadcn-style setup and does not mount in a bare project as copied.

Use it if

  • You want a polished single-file drop zone with file type, size, and custom validation hooks.
  • Your app already uses Tailwind and shadcn-style aliases and can wire the selected file into its own upload service.
  • You need light and dark styling plus animated progress and error feedback in one component.

Skip it if

  • You need real network upload progress out of the box, because the included progress sequence is only a simulation.
  • You need multiple-file selection, queued uploads, retry controls, or resumable transfers.
  • You want a dependency-light native input and do not want Motion, Lucide, Tailwind utilities, or a local class-name helper.

Install

Installation record for kokonut-file-upload
Declared dependencieslucide-react, motion
Missing on installnone
Bare installfails once the shadcn-style helpers are removed, so it needs that setup
Providerno provider required in the harness

In a non-shadcn project, add Tailwind with dark-mode support, install Motion and Lucide React, configure the at-sign path alias, and provide a cn class-merging utility under the local lib path. Keep it as a client component, then replace or bypass the simulated progress flow when connecting real storage.

Source and credit

This page is a review, not a copy. The component source lives with its author and this site does not republish it. Read the license before you use anything.

Alternatives

Other published entries for the input pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.