-
Notifications
You must be signed in to change notification settings - Fork 26
-
Notifications
You must be signed in to change notification settings - Fork 26
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
The guard is awfully finicky. #12
Comments
It looks like you're the first one after over 30'000 downloads who uses this Guard and does not use different source and target directories. You could have avoid your troubles by just adding an output directory, as described in my response to you in #11 or in the README. The problem was a wrong implementation to fix #11 and I finally fixed it now correctly and added the missing spec I omit last time (my bad!). Version 0.5.6 is released for you. |
I've tried setting |
You're right, that is only working when supplying a directory. I'm sorry about that. |
Nice. Thanks. |
:hide_success shows success notification after a failure
Using
... I'd expect each
.coffee
file to be compiled into an appropriate.js
file in each respective directory, similar to every other guard that compiles something. Instead all the .js gets compiled into the top-level directory. Am I missing something?The text was updated successfully, but these errors were encountered: