Page saying `500: Page not found` with Adblocker browser extension

[999bits]

Describe the bug

I'm working on vite+sveltekit project and when I install dependencies and run on my local, it says 500: Page not found. The deployment on vercel has no problem at all and it worked as expected. Turns out, my adblocker blocked me working from local. Here's the link to extension.

Reproduction

Reproduction project can be any svelte kit project with site.

Logs

No response

System Info

System:
  OS: macOS 14.5
  CPU: (8) arm64 Apple M2
  Memory: 185.92 MB / 24.00 GB
  Shell: 5.9 - /bin/zsh
Binaries:
  Node: 16.20.2 - ~/.nvm/versions/node/v16.20.2/bin/node
  Yarn: 1.22.22 - /usr/local/bin/yarn
  npm: 8.19.4 - ~/.nvm/versions/node/v16.20.2/bin/npm
Browsers:
  Chrome: 126.0.6478.127
  Safari: 17.5
npmPackages:
  @sveltejs/adapter-auto: 1.0.0 => 1.0.0 
  @sveltejs/adapter-vercel: ^1.0.0 => 1.0.6 
  @sveltejs/kit: 1.30.4 => 1.30.4 
  svelte: ^3.55.0 => 3.59.2 
  vite: 4.5.3 => 4.5.3

Severity

serious, but I can work around it

Additional Information

No response

[Conduitry]

I also have uBlock Origin installed, and it's not causing any problems for me with running SvelteKit applications locally in dev mode. We'll need a more specific reproduction. What's being blocked?

[999bits]

@Conduitry Thank you for coming up shortly. For the additional context, I'm using pnpm for package installation and Pug for the rendering utils. If I disable or remove the chrome extension and refresh the page, it works awesomely.

[999bits]

@Conduitry One more, I can make page displaying by downgrading several packages, but this prevents me clicking any of the components on the page. Is this related to Pug?

[gterras]

@Conduitry Thank you for coming up shortly. For the additional context, I'm using pnpm for package installation and Pug for the rendering utils. If I disable or remove the chrome extension and refresh the page, it works awesomely.

Make sure you don't have a route that includes /ad/ or something like that. Also worth deleting browser data for localhost and deactivating service worker.

[dominikg]

reproduction is required, otherwise we won't be able to check if it is a bug in sveltekit. More than likely it is a problem with your ublock setup, but without giving us any information it's impossible to tell.

A link to a repository, or a fork of https://node.new/sveltekit, that reproduces the issue. Reproductions must be short, self-contained and correct and must not contain files or code that aren't relevant to the issue — please do NOT just paste a link to your project. Explaining how to reproduce is generally not enough. It pushes the burden of creating a reproduction project onto a small set of volunteer maintainers and isn't scalable. If no reproduction is provided, the issue will be closed.

In addition to that repo, we need a log from ublock which urls specifically it blocked, or any non-standard setting you enabled for it.