buildSteps keyed every untagged log entry by its own pf_logid, so a version with two dozen routine untagged scale/recode passes drew two dozen separate bars -- one per operation, none of them named. The ledger in OperationPanel.jsx already collapses these into a single "N untagged adjustments" line; Bridge now does the same, and groups tagged entries case-insensitively too, carrying the most-used spelling as the label, matching the ledger's own grouping exactly. The old per-row "untagged"/"×N" captions are dropped where they'd now just repeat what the collapsed label already says. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| public | ||
| src | ||
| vendor | ||
| .gitignore | ||
| eslint.config.js | ||
| index.html | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| vite.config.js | ||
React + Vite
This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Oxc
- @vitejs/plugin-react-swc uses SWC
React Compiler
The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.
Expanding the ESLint configuration
If you are developing a production application, we recommend using TypeScript with type-aware lint rules enabled. Check out the TS template for information on how to integrate TypeScript and typescript-eslint in your project.