Fix esbuild 0.24.1 issue

[AlperGurel]

Describe the bug
wasp start command fails on a newly created example to do project. With this error. I have been using wasp for over a month now, my project failed today with an error. When I try new project from wasp, it also failed.

To Reproduce
Steps to reproduce the behavior:

1. Enter wasp new in terminal.

2. Select todo-ts app by pressing 2 and enter.

3. Type wasp db migrate-dev

4. Type wasp start

Expected behavior
I should be able to see the app start successfully.

Screenshots

Desktop (please complete the following information):

• Macos Sonama (M2 Chip)

Additional context
People over internet mention it is an esbuild problem so they were able to solve it by downgrading esbuild, but it didn't work for me.

[infomiho]

I can confirm this also happens what I do the steps you described 👍 thank you for the report

Esbuild team track this here: evanw/esbuild#4010
Vite team tracks this here: vitejs/vite#19018

It should be fixed by this PR: evanw/esbuild#4013 (I suppose this will be then released in the next esbuild release).

Let's see if this get released today and that should be it. If it doesn't happen, we should quickly patch this since Wasp is now broken and you can't really work on new apps!

[hugomartinet]

Hi @infomiho,
Thanks for your report! Do you know of a way to bypass this issue in the meantime? Can we somehow tell wasp to use a previous version of esbuild?

I tried 2 options, but none worked..

1. Forcing vite version to a previous version

{
  "name": "my-app",
  "dependencies": {
    ...
  },
  "devDependencies": {
    ...
    "vite": "4.2.0"
  }
}

2. Overriding esbuild version in the vite dependencies

{
  "name": "my-app",
  "dependencies": {
    ...
  },
  "devDependencies": {
   ...
  },
  "overrides": {
    "vite": {
      "esbuild": 0.24.0
    }
  }
}

[patak-dev]

vite@6.0.5 is out pinning to esbuild 0.24.0 until this is fixed in esbuild, you can update to vite instead of doing the override

[infomiho]

Thank you @patak-dev! This fixed our problem now :)

Wasp now works again @AlperGurel but we are still going to look into pinning some of our deps (e.g. Vite or our Rollup plugin for bundling the server) in the future.