Four more mutations had no error feedback: equipment condition change, task completion, and notification mark-as-read all failed silently. More importantly, the offline sync badge computed a result.failed count from syncPendingInspections() but never displayed it - an entry rejected by the server (e.g. a validation rule) would sit in the offline queue indefinitely with zero indication to the beekeeper why it never syncs. Both the failed-count and outright sync-mutation rejection now surface a toast. Co-Authored-By: Claude Sonnet 5 <[email protected]>
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.