"The service was stopped"

[zandargo]

Describe the bug

Just started the project with pnpm install && pnpm run dev.
It install the packages, start to run Quasar and sudenly logs "The service was stopped".

It does not occur in my local machine and neither with other quasar projects I tested in Stackblitz

Link to the blitz that caused the error

https://stackblitz.com/~/github.com/zandargo/qsr-floworks-studio?view=editor

Steps to reproduce

Just started the project with pnpm install && pnpm run dev.
It install the packages, start to run Quasar and sudenly logs "The service was stopped".

Expected behavior

Expected it to run and display in preview window.
It did a couple days ago. Since then, no major changes were made.
It runs fine both locally and in Codesandbox.

Parity with Local

• I have run the project in my local machine and I could not reproduce the issue.

Screenshots

No response

Platform

Version = 1.84.0
Hash = 3b0b7194bc6b567c2eaf4c96a5759098469dcf59
WebContainer = dcbe33f5

Browser name  = Chrome
Full version  = 135.0.0.0
Major version = 135
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 110645743,
  "usedJSHeapSize": 104430923,
  "jsHeapSizeLimit": 4294705152
}

Additional context

No response

[SamVerschueren]

Hey @zandargo! The project either doesn't exist or the repo is private. Can you share a public repository?

[zandargo]

Hey @zandargo! The project either doesn't exist or the repo is private. Can you share a public repository?

This is my only quasar repo having this issue. I don't wish to make this repo public, but I could grant you access... Would that be ok?

[SamVerschueren]

Sure, that works as well!

[zandargo]

Done. I sent you the invite.

[SamVerschueren]

I looked into this and I found out that it's because of the esbuild version.

tl;dr: Add "esbuild": "0.15.18" to your resolutions field in package.json

Because esbuild is a native dependency, we can't run that in the browser. However, esbuild also publishes a WebAssembly version (esbuild-wasm) which is the one we use. When I used the exact same version from esbuild-wasm on local, I also got the message The service was stopped. So this means it's not an issue with WebContainer but rather with esbuild-wasm. Then I upgraded esbuild-wasm to 0.15.18 and it worked. So they must've fixed something on their end. Because esbuild is not a direct dependency of your project, add "esbuild": "0.15.18" to your resolutions field in package.json.

[zandargo]

"esbuild": "0.15.18"

It worked! Thank you so much. =)