Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Shouldn't try to do a client refresh unless using autoupdate #3365
I'm encountering a very strange issue when working on the Q42 website (http://github.com/q42/q42.nl) -- and nowhere else. Whenever I change a client-side file such as HTML, JS, CSS etc. the terminal will print the following:
The server will restart, which takes around a minute, and the CSS live injection or hot reload features don't work. I have to manually refresh the page. This is making it very hard to work quickly. I was hoping the work that went into speeding things up with 1.0.2 would resolve it, but it's still happening and I haven't been able to isolate the issue.
Posting it here in case anyone has some pointers on what to do to isolate it, has encountered something similar, or knows how to debug it.
FYI, I'm running the site on port 80 using
@adnissen Thanks! I started this project in December 2012 or so. I've been upgrading it over time, but it's entirely possible that in transitioning I didn't make the upgrade as smoothly as Meteor itself would have. Feels silly that I didn't realise this would be the problem. Awesome!
I suppose this is arguably a bug --- perhaps we shouldn't try to do the client-reload unless the app includes autoupdate?