1cbd1c72fa
* fix(colab): pin torchvision==0.23.0 to resolve torchvision::nms operator missing error (#1357) This resolves the runtime import failure of transformers.HiggsAudioV2TokenizerModel due to torchvision mismatch with torch 2.8.0. Changes: - pyproject.toml: Added torchvision>=0.19 to dependencies, pinned to 0.23.0 in constraint-dependencies, and configured the pytorch-cuda source index. - uv.lock: Regenerated lockfile to resolve torchvision 0.23.0+cu128. - bootstrap.rs: Added torchvision to rocm_torch_reinstall_args and updated the matching unit test. * fix(bootstrap): pin versions in ROCm reinstall path and add CHANGELOG entry (#1358) * test(rocm): pin bootstrap.rs to pyproject constraint, mechanically The PR adds a "Keep in sync with [tool.uv.constraint-dependencies]" comment above rocm_torch_reinstall_args. That is the right instruction and a comment cannot enforce it, so it becomes a test — CLAUDE.md`s convention is that a rule a reviewer has to remember belongs in one. It matters more here than the usual lockstep case: an AMD user`s install does not come from uv.lock at all. bootstrap.rs shells out to pip against the ROCm index, so whatever it names there is the Torch stack that user actually runs, and a drift produces no install-time error — it surfaces later as "operator torchvision::nms does not exist" or a silent CPU fallback, which is #972 and #1357 from two different directions. Three cases: the constraint block still pins the trio (so the rest cannot pass vacuously), the ROCm pins equal it, and all three are reinstalled together — a subset leaves the others on CUDA wheels the ROCm build cannot pair with. Both drift cases fail against the previous, unpinned form. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: debpalash <4178343+debpalash@users.noreply.github.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.