[vite] Internal server error: Cannot read properties of undefined (reading 'endsWith')

[Nefcanto]

Describe the bug

I'm trying to create the blog page using Qwik at example.local/blog but I see this error:

[vite] Internal server error: Cannot read properties of undefined (reading 'endsWith')

I also sent it to the Qwik team. But since it says vite, I sent it here too.

The problem is that it does not give us any more information whatsoever. Just one vague line. We're stuck at debugging it.

We need the call stack to be able to debug this. And that call stack should also contain info related to our code too. Because just seeing the call stack of vite internal won't help either.

Reproduction

https://github.com/Nefcanto/ViteQwikEndsWith

Steps to reproduce

• Clone
• npm install
• npm run dev
• Go to locahost:port/blog, you should see the error

System Info

System:
    OS: Linux 5.15 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
    CPU: (4) x64 Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
    Memory: 8.86 GB / 15.52 GB
    Container: Yes
    Shell: 5.1.4 - /bin/bash
  Binaries:
    Node: 18.14.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.4.2 - /usr/local/bin/npm
  npmPackages:
    vite: ^4.1.1 => 4.1.1

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sapphi-red]

I was not able to reproduce. I only got the following error in the browser console.

GET http://localhost:5173/manifest.json 404 (Not Found)
manifest.json:1 Manifest: Line: 1, column: 1, Syntax error.

Closing as it seems this issue is solved on Qwik side: QwikDev/qwik#2878