Skip to content

[Due for payment 2025-08-13] [$375] Figure out why webpack-dev-server is crashing #65082

Closed

Description

@roryabraham

Background

webpack-dev-server often crashes during development

Problem

When webpack-dev-server crashes, it wastes time, causes confusion and frustration.

Solution

Figure out why it's crashing, fix it.

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021938625189265279504
  • Upwork Job ID: 1938625189265279504
  • Last Price Increase: 2025-07-29
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @CortneyOfstad

Activity

  1. self-assigned this
    on Jun 27, 2025
  2. added
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jun 27, 2025
  3. changed the title [-]Figure out why webpack-dev-server is crashing[/-] [+][$250] Figure out why webpack-dev-server is crashing[/+] on Jun 27, 2025
  4. melvin-bot commented on Jun 27, 2025

    @melvin-bot
  5. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jun 27, 2025
  6. melvin-bot commented on Jun 27, 2025

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @DylanDylann (External)

  7. melvin-bot commented on Jun 27, 2025

    @melvin-bot

    Triggered auto assignment to @CortneyOfstad (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  8. toquanghieu commented on Jun 27, 2025

    @toquanghieu

    hi bro, i cannot access the link https://stackoverflow.com/c/expensify/questions/14418 to see detail

  9. melvin-bot commented on Jun 27, 2025

    @melvin-bot
  10. toquanghieu commented on Jun 27, 2025

    @toquanghieu
  11. melvin-bot commented on Jun 27, 2025

    @melvin-bot
  12. 62 remaining items

  13. melvin-bot commented on Aug 6, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  14. melvin-bot commented on Aug 6, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.89-21 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2025-08-13. 🎊

    For reference, here are some details about the assignees on this issue:

    • @ikevin127 requires payment through NewDot Manual Requests
    • @DylanDylann requires payment through NewDot Manual Requests
  15. melvin-bot commented on Aug 6, 2025

    @melvin-bot

    @ikevin127 / @DylanDylann @CortneyOfstad The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  16. ikevin127 commented on Aug 11, 2025

    @ikevin127
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other: Development (DX)

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: No specific PR is responsible as this was the result of the original design.

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: N/A

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    ✅ No need for a regression test since the issue is related to local developer experience (DX) and the PR had [NoQA].

    Do we agree 👍 or 👎.

    cc @CortneyOfstad

  17. melvin-bot commented on Aug 13, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@CortneyOfstad)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1938625189265279504/hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  18. OfstadC commented on Aug 14, 2025

    @OfstadC
    Contributor

    Payment Summary here is accurate.

    Upwork job closed - no regression testing needed

  19. garrettmknight commented on Aug 14, 2025

    @garrettmknight
    Contributor

    $375 approved for @ikevin127

  20. quinthar commented on Oct 17, 2025

    @quinthar
    Contributor

    Approved $375 to @DylanDylann

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.ExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions