Paul Trowbridge
89026e3440
Autofill filled only empty boxes, so it appeared to work exactly once. Type a part, get its nine attributes; type a different part, and every box is already full, so nothing updates and the form still describes the previous part. That is worse than blank -- the recode would have been submitted with one part's code and another's attributes. These columns describe the key that was just entered, so they are replaced outright now. A lookup that finds nothing also said nothing, which is indistinguishable from a lookup that did not run. It warns, and names the value it could not find, so an unknown part reads differently from a broken autofill. Co-Authored-By: Claude Opus 5 (1M context) <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.