Errors in default, empty webpack project: Uncaught (in promise) - Could not establish connection. Receiving end does not exist.

I’m submitting a bug report

• Library Version: 0.33.1

Please tell us about your environment:

• Operating System: macOS 10.13.5

• Node Version: 8.9.4

• NPM Version: 5.5.1

• Browser: Chrome 67.0.3396.87 (Official Build) (64-bit)

• Language: TypeScript 2.5.2

• Loader/bundler: Webpack

Current behavior: On starting a new, Default TypeScript project (with Webpack), without any modifications, my Google Chrome browser throws the following errors multiple times:

Uncaught (in promise) {message: “Could not establish connection. Receiving end does not exist.”} [browser-polyfill.js:610]

• What is the expected behavior? Expected behaviour is not having any console errors.

Steps to reproduce:

1. Run au new to create a new app (with CLI v0.33.1), giving it name foo
2. Choose options 2 => 1 => 1 to create a Default TypeScript project and install all dependencies
3. Navigate to folder, cd foo and run au run --watch
4. Open the browser and the console errors pop up, on my system

[hanssens]

I think I found the cause - and the solution to this. I asked a colleague to try and reproduce the problem. Without success. He ran pretty much the same configuration as me.

I started playing around with my Chrome Extensions, disabling them one-by-one, and the problem was resolved once I disabled the Selenium IDE extension.

For me this fixes it, therefor I’ll close this issue.

[mekbiba]

In my case, it was Adblock Plus, I was testing a vuejs application so i had to white-list the domain.