
In Progress
Posted
Paid on delivery
I’ve built a small React-based expense tracker to manage costs for my candle-making business. It’s a single-page app that stores everything in localStorage—about 800 lines of code in a private GitHub repo I’ll share once we start. Most of it works, but three glitches are blocking me: • The running total is treating numbers as strings, so $12.50 and $30 show up as “12.5030” instead of $42.50. • When I filter by month and delete an expense, the wrong entry disappears. • Any expense dated on the 1st of a month ends up listed under the previous month. I need clean, well-commented fixes that leave the overall structure intact—no major rewrites, just solid JavaScript and React troubleshooting. Please commit your changes to a feature branch, include a short note or PR description outlining what you touched, and verify everything works smoothly across Chrome, Safari, and mobile browsers. Timeline is tight: I have to send numbers to my accountant in 2–3 days, so I’ll be reviewing PRs quickly. If you’re comfortable debugging React components that rely on hooks and localStorage (no backend), I’m ready to give repo access right away.
Project ID: 40802288
306 proposals
Remote project
Active 6 days ago
Set your budget and timeframe
Get paid for your work
Outline your proposal
It's free to sign up and bid on jobs

Hi there, Debugging React state and array manipulation issues under a tight deadline can be stressful, especially when your accountant is waiting on the numbers and incorrect deletions or date offsets mess up your financial tracking. I can quickly resolve these three specific glitches in your expense tracker without touching your core architecture. Before we dive in, here are my questions: 1. Are you using native JavaScript date objects or a library like date-fns/moment to handle the month filtering and the first-of-the-month offset? 2. Are the items in state mapped with unique IDs, or are you currently deleting them using their array index, which causes the wrong entry to vanish when filtered? Drop me a message so we can get started right away.
$80 CAD in 2 days
3.0
3.0
306 freelancers are bidding on average $123 CAD for this job

Hello — I’d fix this in your existing React app without changing the structure: the total needs explicit number parsing, the delete action is likely using a filtered index instead of a stable item ID, and the month issue usually comes from Date timezone parsing on day 1. That approach fits your brief because the app is localStorage-based, hook-driven, and only 800 lines, so this is a targeted debugging pass rather than a rewrite. - Fix totals, delete logic, and month grouping with minimal code changes. - Keep comments clean and add a short PR note on every touched part. - Commit everything to a feature branch in your private GitHub repo. - Verify behavior in Chrome, Safari, and mobile browsers before handoff. I can start from the repo review and isolate each bug against the current state logic first. Is the delete action keyed by array index right now? Roman
$210 CAD in 1 day
9.7
9.7

JavaScript and frontend troubleshooting are central to my work, making this React expense tracker bug fix a strong fit. I can address the string-concatenation total, the incorrect deletion after month filtering, and the date-boundary issue while preserving your existing single-page structure rather than introducing unnecessary rewrites. My frontend development experience covers HTML5, JavaScript, and web development, supported by a 60+ professional in-house team with development and QA capabilities. I can provide clean, well-commented changes suited to a hooks and localStorage-based application, commit them to a feature branch, and include a concise PR note describing the fixes. I can also verify the behavior across desktop and mobile browser scenarios, including Chrome and Safari. Choose me for a focused, dependable debugging pass that keeps your tracker practical and ready for accountant review.
$140 CAD in 7 days
8.2
8.2

These three bugs are common in localStorage-based React apps, and I can name the likely cause of each before opening your repo. The total breaks because values come back from inputs and localStorage as strings, so I'll convert them with Number() before the reduce. The wrong delete is almost certainly the index from the filtered list being applied to the full array, and I'll switch it to delete by a unique ID. The 1st-of-month issue comes from new Date("YYYY-MM-DD") being read as UTC midnight, which I'll fix by parsing the date as local time. I'll add short comments, commit to a feature branch with a clear PR description, test on Chrome, Safari and mobile, and can start immediately.
$30 CAD in 1 day
8.2
8.2

Hi there, We understand you need help fixing bugs in your React-based expense tracker, specifically issues with the running total, filtering by month and deleting expenses, and incorrect month listing for expenses dated on the 1st. Our team at Webbook Studio has experience with JavaScript, React, and frontend development, including debugging and troubleshooting. We've worked on similar projects, such as a learning platform website for children and a website for an electric bike company, both using React and custom design. We'll deliver clean, well-commented fixes that leave the overall structure intact, and we'll verify that everything works smoothly across Chrome, Safari, and mobile browsers. One question: are there any specific coding standards or best practices you'd like us to follow while making these fixes? Feel free to message us to discuss the details! — Webbook Studio
$250 CAD in 3 days
8.1
8.1

Your three bugs point to separate issues in number handling, filtered-list identity, and date parsing. I can fix them without changing the app’s structure or disturbing your existing localStorage data. I’ll convert expense amounts to numbers before totaling them, trace deletion back to the correct record rather than its position in a filtered list, and handle expense dates as local calendar dates so entries on the 1st stay in the right month. I’ll add focused regression checks for each case, keep comments where they clarify the fix, and verify the flows in Chrome, Safari, and mobile browsers. I’ll commit the changes to a feature branch with a short PR description explaining what changed and how I tested it. Can you share repo access and one example of how an expense date is stored in localStorage?
$50 CAD in 3 days
7.5
7.5

React frontend debugging is a core part of my 12+ years in website, software, and custom web development, and your expense tracker’s issues are well matched to my JavaScript and debugging skills. I work with React-based applications and can address the string concatenation, filtered deletion, and month-boundary date bugs while keeping the existing structure intact. My experience includes custom-coded development, responsive web development, and full website testing and QA. That is directly relevant to checking hooks, localStorage data handling, date parsing, totals, and behavior across desktop and mobile browsers. I can also provide clean, well-commented fixes and a concise PR description documenting the changes, with the work committed to a feature branch. I’m ready to apply focused troubleshooting to this React app and help you get dependable expense totals and filtering for your accountant review. Choose me for a careful, practical fix without an unnecessary rewrite.
$178 CAD in 1 day
7.3
7.3

Hello!, I am a US-based senior software engineer and I’d be glad to fix your React expense tracker so it’s reliable for day-to-day use in your candle business. The main pain point here is usually not just “bugs” but broken flows that slow down real work: adding expenses, editing entries, totals not matching, or Chrome-specific issues. I’ll start by tracing the issue in the UI, checking the console/network behavior, then patch the root cause instead of applying quick hacks. After that I’ll verify the tracker across key actions, clean up any fragile state handling, and make sure it behaves consistently. I’m detail-focused, so I’ll treat this like a small production app, not a throwaway script. If needed, I can also suggest a couple of practical improvements so the tracker is easier to maintain going forward. Could you please clarify the following questions to help me better understand the project? 1. Which exact bug(s) are showing up right now, and what should happen instead? 2. Is the app using local state only, or does it save data somewhere like localStorage, Firebase, or an API? 3. Do you want me to keep the current structure/UI intact, or is small cleanup refactoring okay? Relevant work I’ve done includes: a React invoice dashboard, a Chrome extension for internal ops, a small inventory tracker for a retail business, and a budgeting app for a service company. James Zappi
$140 CAD in 1 day
7.1
7.1

Hello, I can carefully troubleshoot the three React expense-tracker issues while preserving your existing structure: numeric coercion for accurate totals, stable expense identifiers for correct deletion after filtering, and timezone-safe date handling for expenses on the first of each month. I’ll keep the fixes clean and well-commented, commit them to a dedicated feature branch, and provide a concise PR summary of every change. I’ll also verify the key flows across Chrome, Safari, and mobile browsers, with particular attention to hooks, filtering, deletion, localStorage persistence, and edge-case dates. A useful improvement would be adding focused regression checks for these three scenarios to prevent recurrence. Regards Muhammad
$110 CAD in 2 days
6.6
6.6

Hi there, I immediately see that the issue with the running total concatenating strings instead of summing them is crucial. I can help you fix this with a clean reassessment of how to handle state in your component, ensuring numerical values are processed correctly, especially when interfacing with localStorage. Furthermore, I'll also dive into the filtering logic to correct the deletion of expenses and address the date handling for expenses on the 1st of the month. I’ll ensure to follow your request for well-commented code and commit the changes to a feature branch, including a detailed PR description for clarity. With a tight timeline of 2-3 days, I’m prepared to start right away and verify that everything functions perfectly across the specified browsers. Regards, Ali
$55 CAD in 1 day
6.6
6.6

Hi, I can fix all three React bugs while preserving your existing app structure. I’ll correct numeric handling in the running total, fix filtered expense deletion using stable IDs, and resolve the month-boundary issue with consistent local date parsing. **Deliverables:** Clean, commented fixes; feature-branch commits; a concise PR summary; and testing of totals, filtering, deletion, and date handling across Chrome, Safari, and mobile browsers. Can you share the current app structure and any steps to reproduce the issues? Ready to start ASAP.
$140 CAD in 2 days
6.7
6.7

Hi there, I’ve read your project description and understand that you need help fixing three React expense tracker bugs involving numeric totals, filtered deletion, and month/date handling. I can help you achieve this with clean, targeted React and JavaScript fixes that preserve your current structure. I have strong experience in React.js, JavaScript, HTML5, debugging, and Git, including client work resolving JavaScript issues and developing web app features. My approach: - Review the components, hooks, localStorage flow, and filtering logic carefully. - Correct numeric parsing/calculation, stable expense identification during filtered deletes, and date/month handling. - Keep changes focused and well commented, without a major rewrite. - Commit the work to a feature branch and provide a concise PR note describing the fixes. - Verify the main flows in Chrome and check responsive/mobile browser behavior as requested. I understand your accountant deadline and can prioritize a prompt, reliable fix. Could you please clarify whether expense IDs are currently stored with each localStorage record, or are list indexes used for deletion? Thank you for your time. I look forward to working with you! Best regards, Teo
$150 CAD in 2 days
6.6
6.6

Hi, Your React expense tracker has 3 bugs blocking you: numbers are concatenating as strings instead of summing, the wrong expense disappears when you filter by month and delete, and expenses on the 1st show under the previous month. You need clean fixes that keep the structure intact and work across Chrome, Safari and mobile. Here's how I'll fix it: First, check how expenses are stored in localStorage and where totals are calculated, numbers likely need parseInt or parseFloat before addition. Then, debug the filter and delete handlers to find why the wrong expense is removed when a month filter is active, checking array indices and state updates. Finally, inspect the date parsing logic for month assignment, test the 1st-of-month edge case, then verify all fixes work across Chrome, Safari and mobile browsers. I take a full backup first, then test everything on desktop and mobile so you see it working before we close. Let me know if you'd like to move forward with this plan. Best regards, Salma Noreen
$250 CAD in 3 days
6.8
6.8

Hello, I can help you resolve the issues with your React expense tracker for your candle-making business. From what you’ve described, it sounds like you need to address a few key bugs: fixing the running total calculation, ensuring the correct expense is deleted when filtered by month, and correctly associating expenses with their respective months. I’d approach this by carefully reviewing the relevant code sections, making targeted adjustments, and ensuring everything is well-commented for clarity. With 7+ years of experience in JavaScript and React, I’m confident in troubleshooting these types of issues without major rewrites. I’ll ensure your app functions smoothly across different browsers as well. One question I have is whether there are any specific edge cases you’ve noticed with the current filtering and deletion functionality? Best regards, Ivan Mandinski
$140 CAD in 2 days
6.7
6.7

The 1st-of-month shift is usually a UTC date parse, and Safari reads those strings differently from Chrome, so a Chrome-only fix would still miss. Plan: feature branch with all three fixes and a PR note within 24 hours, checked in Chrome, Safari and mobile, leaving a day or more for your review before the accountant deadline. Totals already saved as strings in localStorage will also be handled, so old entries stay correct. 1. Does each expense carry a unique id, or is it identified by its position in the list? 2. Should existing saved entries be normalized, or only new input fixed? Ready to start on the branch the moment repo access arrives.
$110 CAD in 3 days
6.7
6.7

Expenses on the 1st landing a month early usually means new Date("2025-03-01") parsing as UTC midnight. West of UTC that's the day before, so I'd parse dates locally. The 12.5030 total means localStorage returns strings, so amounts need Number(). The wrong delete is likely a filtered-list index hitting the full array, so I'd delete by id. Tested in Chrome, Safari and mobile, the PR comes 1 day after repo access, before your accountant deadline. Which timezone are you in?
$100 CAD in 1 day
6.7
6.7

Hi, The string concatenation on the running total and the month filter bug both point to how the expense data is being parsed and compared—likely missing parseInt or parseFloat calls when reading from localStorage, and the month filter probably comparing strings instead of date objects. The 1st-of-month issue suggests the date parsing is off by one day, possibly a timezone or day-of-month boundary problem in how the filter calculates which month an expense belongs to. I'd start by tracing the add expense flow to fix the number parsing, then check the filter logic to ensure it compares actual dates, not strings. For the month boundary bug, I'd log what the filter sees for expenses on the 1st and adjust the date math. I'll test all three fixes across Chrome, Safari, and mobile by adding and deleting expenses, filtering by different months, and checking the totals update correctly each time. I'll commit to a feature branch with a clear PR description for each fix so your accountant review goes smoothly. Send the repo link and I'll start with the localStorage parsing in your expense component. Denis
$150 CAD in 3 days
6.4
6.4

React bug fixing and JavaScript debugging are directly aligned with the issues blocking your expense tracker. My 8+ years in website development, combined with React, JavaScript, frontend development and debugging skills, position me to correct the calculation, filtered deletion, and month-boundary problems while keeping your existing single-page structure intact. I can work comfortably with React components, hooks, browser-based functionality and local data storage, including the type conversion and date-handling issues behind the incorrect totals and month grouping. I will keep the fixes clean and well commented, commit them to a feature branch, and provide a concise PR note describing the changes. My frontend development background also supports checking the result across Chrome, Safari and mobile browsers. Choose me to stabilise the tracker quickly and deliver focused fixes without an unnecessary rewrite.
$179 CAD in 1 day
6.6
6.6

Hi, I can help stabilize your React expense tracker quickly while preserving its current structure. I’ll correct numeric coercion in the running total, make filtered deletions target stable expense IDs, and fix the month-boundary timezone issue affecting dates on the 1st. I’ll keep the changes clean and commented, test hooks and localStorage behavior across Chrome, Safari, and mobile browsers, then commit everything to a feature branch with a concise PR summary. A useful improvement would be adding focused regression checks for totals, filtered deletion, and timezone-safe date grouping so these bugs do not return. I’m ready to review the repository and prioritize the fixes for your accountant’s deadline. Check out my portfolio here:- https://www.freelancer.com/u/installerpoint Best Regards, Muhammad Adeel
$90 CAD in 2 days
6.6
6.6

All three bugs trace back to data handling, not your React structure. The 1st-of-month bug is classic: new Date("2024-03-01") parses as UTC midnight, so anywhere west of UTC it lands in the prior month and skews your accountant's numbers. Quick questions - does each expense carry a unique id, or does delete rely on array index? And should I clean up existing localStorage entries saved as strings so older data totals correctly? Here is the architectural approach: - STRING TOTALS: Coerce amounts with Number() on save and inside the reduce, then format with toFixed(2) so $12.50 + $30 shows $42.50. - FILTERED DELETE: Delete by stable id instead of the filtered list index, backfilling ids for legacy entries without touching your hooks. - DATE PARSING: Parse YYYY-MM-DD as local time and verify in Chrome, Safari and mobile brows
$130 CAD in 3 days
7.1
7.1

React.js and JavaScript are central strengths of my work, backed by senior software engineering experience serving clients since 2015. Your expense tracker’s string-total, filtered deletion, and month-boundary issues are well suited to focused troubleshooting in a hooks- and localStorage-based single-page application. My frontend development background includes building websites and applications from scratch, with practical experience across ReactJs, JavaScript, HTML, JSON, and related web technologies. I will keep the existing structure intact, provide clean and well-commented fixes, and document the touched areas in the feature-branch commit or PR description. I can also verify the corrected behavior across desktop and mobile browser contexts, including Chrome and Safari. I’m ready to apply careful debugging rather than introduce an unnecessary rewrite, and I would be glad to resolve these blockers so your expense figures are dependable for your accountant.
$140 CAD in 3 days
6.3
6.3

Ottawa, Canada
Payment method verified
Member since Oct 21, 2026
₹600-1500 INR
₹12500-37500 INR
₹12500-37500 INR
₹1500-12500 INR
$750-1500 USD
₹1500-12500 INR
€30-250 EUR
$30-250 AUD
$250-750 USD
$15-25 USD / hour
₹37500-75000 INR
$250-750 USD
$8-15 AUD / hour
$25-50 USD / hour
$8-15 USD / hour
₹12500-37500 INR
$10-20 USD
₹12500-37500 INR
₹600-1500 INR
$250-750 USD