Jeff
AFAIK this is still very much a blocker still, it can't really be worked around.
Just commenting to confirm this behaviour in my project too. I'm not sure what change needs to be made here, however.
@developit Yeah, I am running them on different ports. Apologies for leaving out that crucial detail 😅 I have updated the original question too. I have just tried using vastly...
Here is a little script to reproduce the issue: ```shell # Create 2 projects preact create default app_a; preact create default app_b; # Setup app A cd app_a; sed -i...
Apologies @developit I'm not sure the script I posted in my previous comment works properly. I've updated it here. It also installs the latest versions of `preact` and `preact-cli` in...
Unrelatedly, I was wondering if y'all wanted to chuck the [Hacktoberfest](https://hacktoberfest.digitalocean.com/) topic on this repo? This would make this PR count towards my "score" on there, and might bring in...
Thanks for taking the time to review @rschristian, I thought this would never be looked at
+1, started getting the same issue across all my projects with the following configuration: ``` Windows Server 2012 R2 Standard Chrome 52.0.2743.82 m karma 0.13.22 karma-chrome-launcher 1.0.1 ``` Not using...
53.0.2785 also working on our server
So what's the status of this (and the OSX build)? There are branches for it but they aren't yet working? Seems like the Linux branch still has a whole pile...