Files
fancy-dns/web
developer f24fd63e9a web: give the toast helper a real type and keep the dist bundle out of git
Blocklists, Clients, Domains and Upstreams each carried a ToastLike shim
that duck-typed a react-hot-toast style API. The console uses its own
Toast context, so notify() was calling toast('some message') with a string
where ToastOptions is expected: every mutation toast rendered an empty
title. They now take the toast function from useToast() and send a real
{ title, tone } payload, mapping 'fail' onto the danger tone.
2026-09-27 11:32:39 +00:00
..
2026-09-27 11:20:34 +00:00
2026-09-27 11:20:34 +00:00
2026-09-27 11:20:34 +00:00
2026-09-27 11:20:34 +00:00
2026-09-27 11:20:34 +00:00
2026-09-27 11:20:34 +00:00
2026-09-27 11:20:34 +00:00
2026-09-27 11:20:34 +00:00
2026-09-27 11:20:34 +00:00
2026-09-27 11:20:34 +00:00
2026-09-27 11:20:34 +00:00
2026-09-27 11:20:34 +00:00

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:

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.