Rows that slide into their sorted order, a selection, and a delete that asks and can be undone.
The prompt17,950 characters
Add the "Table" component from notboring to my project.
It is licensed for use in my projects — notboring.dev/license. Please:
1. Create the component at a sensible path for this
project, named Table, from the source below.
2. Install what it needs: npm i framer-motion lucide-react
3. Add the CSS to the project's stylesheet.
4. THE PART THAT NEEDS YOUR JUDGMENT. The CSS reads
these custom properties and does not define them:
--card
--danger
--danger-rgb
--font-ui
--ink
--ink-2
--ink-3
--ink-4
--ink-rgb
--on-ink
They are notboring's design tokens. Map each one to
whatever this project already uses for the same
job — its own ink, ground, surface and UI font —
rather than defining them as new globals. If the
project has no equivalent, define it locally on
the component's own root so nothing leaks out.
Anything ending -rgb wants three bare numbers,
because the CSS builds rgba() from it.
5. IF YOU CHANGE IT, GO ALL THE WAY. This block is
built for every state its object can really be
in — empty, one, full, refused, undone, pressed
twice, interrupted halfway — and not only the one
the demo opens on. Adapt it and the same standard
holds: work out that list before you write, and
build the whole of it. Never settle for the
minimum that makes the screenshot right. A
component somebody has to come back and finish is
the thing this was written to replace.
Keep the comments. They say why the numbers are what
they are, and they are most of what makes this worth
copying rather than rewriting.
--- Table.tsx ---
import { useEffect, useLayoutEffect, useRef, useState } from "react";
import { motion, useSpring } from "framer-motion";
import { Check, ChevronDown } from "lucide-react";
/* ══ Table ════════════════════════════════════════════════
Five invoices, a column that sorts, rows you can pick, and
a delete that asks — and can be taken back.
ROWS MOVE, THEY ARE NOT REDRAWN. Each row is placed by a
spring on its y, set from its position in the current
order, so sorting is five rows sliding past each other to
where they now belong — not a list that blinks into a new
arrangement. Read in the block's own pixels (an index times
the row height), never from screen rectangles, so it is
right under any transform.
THERE ARE NO LINES. Rows are told apart by their own
height and the wash under the pointer; a chosen row keeps
its wash. Hairlines between rows are the thing a table is
expected to have, and the thing that makes it read as a
spreadsheet.
DELETE HAPPENS IN TWO BEATS, AND THE SECOND CAN BE TAKEN
BACK. Delete becomes its own question in the same place;
The rest — the source and its comments — is what the plan opens.