-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add reloadOnMissingCSS option, see livereload-js. #93
Conversation
Waiting on a response from livereload/livereload-js#41 |
Hi guys, we may put this on hold since livereload/livereload-js#41 is on hold as well. I'm thinking about forking livereload-js to enable us more freedom in the client side. And probably port it to ES6 and babel instead of coffee. |
👍 on forking livereload-js, seems abandoned. Double 👍 on moving to ES6/babel, yay! |
Hi @STRML I'm sorry but I'll close your PR for the moment. As soon as we can have updates from livereloadjs or decide to make and build our own version of livereloadjs, we may reconsider this option. I hope you understand. |
Thanks - but if you consider this on hold, why not keep it open and label On Aug 13, 2016 5:15 AM, "Mickael Daniel" notifications@github.com wrote:
|
Fine, let's keep it opened. This was just in order to clean up old issues / PR |
@STRML might want to rebase while we're waiting, so it's good to go when the upstream gets resolved. |
@STRML would you mind resolving conflict on this branch with a rebase? We finally have a maintainer active in livereload-js and I'm hopeful we can get your upstream PR merged soon so we can finally land this feature! |
@elwayman02 Rebased it - 👍 |
Awesome, thanks! I'll do my best to keep an eye on the upstream PR and get that into tiny-lr asap. |
Corresponding
livereload-js
PR: livereload/livereload-js#41