You’re staring at a laptop screen at 2 a.m., receipts everywhere, wondering if that bulk buy of vintage tees was genius or suicide. Profits? A myth. Attention items? Buried in tabs.
Enter emoney-profit-tracker — a scrappy Next.js 15 app that doesn’t pretend to be the next Salesforce. It just tracks what you buy, what you sell, and what’s actually paying the bills. For resellers juggling platforms like eBay, Depop, and whatever shady Discord group, this nails the pain: “what is actually making money?” and “what still needs attention?”
Why Resellers Can’t Ignore Emoney Profit Tracker Anymore
Look. Spreadsheets lie. They’re fine for one-offs, but scale to 50 listings? Chaos. This app centralizes it all — purchases, sales, trends, even a ‘quests’ system for those nagging tasks like ‘relist expired auctions.’ Built on Next.js App Router, it’s client-heavy where it counts: auth, fetching, filtering. Server? Barely touched. Smart for dashboards, lazy for SEO obsessives.
The layout’s a dream. Global shell in app/layout.tsx with Providers and Toaster. Authenticated zone under (authenticated) — TopNav, MobileNav wrapping pages. Thin routes hand off to beefy clients: DashboardClient, ProductsClient. Keeps files tiny, logic glued to UI.
Services? Whisper-thin. product.service.ts, sales.service.ts — Axios wrappers from _http.service.ts. Fixed baseURL, withCredentials, 401 redirects to login with path saved in sessionStorage. No component pollution.
api.interceptors.response.use( (response) => response, (error) => { if (error.response && error.response.status === 401) { if (typeof window !== “undefined”) { const currentPath = window.location.pathname sessionStorage.setItem(“callbackPath”, currentPath) window.location.href = “/login” } } return Promise.reject(error) } )
That’s gold. Auth expiry? Handled. Toasts? Auto.
React Query wrappers in use-query-resource.ts shine. useGetResource for lists, useModifyResource invalidates on mutate. ProductsClient fetches with key [“products”], delete hits same key — poof, refreshed. No manual cache wrestling.
Local state stays local. Search, tabs, dialogs — component turf. React Hook Form + Zod? Perfect. Cheap registration, explicit validation, sanitized payloads.
Auth’s client-side too. AuthProvider tracks user/authStatus, AuthGuard fetches on mount, redirects with path preserve. Discord OAuth for login. Hacky? Sure. But for indie resellers, who needs middleware pomp?
Is Client-Side Overload a Recipe for Disaster?
Here’s the thing — it’s all client. No server guards rejecting bots pre-hydration. Risky for high-stakes data? Maybe. But resellers aren’t banks. This trades security theater for speed.
Take add-sale-form.tsx. Debounced product lookup, dynamic Zod schema clamping quantity to stock:
- const createDynamicSchema = (maxQuantity?: number) => {
- return z.object({
- quantity: maxQuantity
- ? z.number().min(1).max(maxQuantity,
Quantity cannot exceed ${maxQuantity})- z.number().min(1), }) }
Pre-fills sale_price from purchase_price. Business smarts in the form — where they belong.
Quests proof? Dialog on desktop, Drawer on mobile via useIsMobile(450). File-uploader with react-dropzone, URL.createObjectURL previews, FormData submits. Responsive without frameworks.
Shared tables, I bet, cut repetition. (Content cuts off there — classic OSS tease.)
But wait. Unique twist: this echoes early Basecamp — pre-SaaS bloat. Back when tools solved problems, not subscriptions. Prediction? It’ll spawn a wave of Next.js micro-ERPs for solopreneurs, ditching $99/mo QuickBooks clones. Corporate PR spins ‘enterprise-grade’ — this spits ‘pragmatic-grade.’
Critique time. Client-only auth screams ‘trust me, bro.’ Discord OAuth? Niche win for gamers-turned-resellers, alienates normies. Quests? Cute gamification, but does ‘upload shipping proof’ need badges? Meh.
Still, deployable yesterday. Vercel one-click, Supabase backend implied. No lock-in.
What Makes This Next.js App Tick (And Where It Stumbles)
Punchy organization: route groups, feature clients. No Redux bloat — local state rules.
Mutation flow? useMutation + invalidateQueries everywhere. Effortless.
UI nits: Mobile-first-ish, but 450px breakpoint? Arbitrary. File uploader solid, though.
Dry humor aside — it’s refreshing. Open source dashboards often chase ‘full-stack wizardry.’ This says, ‘Nah, client for interactivity.’ Resellers profit.
Historical parallel: Like Rails’ golden era, before Vite envy. Lean code wins hearts (and forks).
Stretch it. Add server actions? Sure. But don’t. Pragmatism first.
Word on hype: None. No ‘revolutionary’ GitHub README. Just code that works. Rare.
🧬 Related Insights
- Read more: Sriracha: Open-Source Imageboard Resurrects Anon Forums
- Read more: Gallery-dl’s GitHub Exit: DMCA Hits Open-Source Scraper, Codeberg Beckons
Frequently Asked Questions
What is emoney profit tracker? Small Next.js app for resellers — tracks buys, sales, profits, quests. Client-heavy, pragmatic.
How to deploy emoney profit tracker? Vercel push. Pair with Supabase/Postgres. Discord auth ready.
Is emoney profit tracker secure for real money? Client auth’s fine for indies. Beef up for scale — add middleware.
