Christophe Vila
252c8fa0d1
Samples right as recording starts (before the run itself begins) can compute an implausible pace like 50+ min/km from a near-zero speed reading; these are now treated as unknown rather than plotted. The pace/HR domain is also now built from the 2nd-98th percentile of the actual trace instead of true min/max, so an occasional stray point (a brief pause, GPS noise) can't single-handedly stretch the scale and squash the rest of a steady effort -- the target band, which is deliberate data rather than noisy telemetry, is still always fully included. Pace axis ticks always land on a round 30-second mark (7:30, 8:00, 8:30, ...).
React + TypeScript + Vite
This template provides a minimal setup to get React working in Vite with HMR and some Oxlint 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 Oxlint configuration
If you are developing a production application, we recommend enabling type-aware lint rules by installing oxlint-tsgolint and editing .oxlintrc.json:
{
"$schema": "./node_modules/oxlint/configuration_schema.json",
"plugins": ["react", "typescript", "oxc"],
"options": {
"typeAware": true
},
"rules": {
"react/rules-of-hooks": "error",
"react/only-export-components": ["warn", { "allowConstantExport": true }]
}
}
See the Oxlint rules documentation for the full list of rules and categories.