-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Refactor Cake tasks #4440
Refactor Cake tasks #4440
Conversation
…ll CoffeeScript the non-NPM way
…ollowing the same form
…nless it’s explicitly excluded
|
||
buildAnnotatedSource = (watch = no) -> | ||
do generateAnnotatedSource = -> | ||
exec "node_modules/docco/bin/docco src/*.*coffee --output docs/v#{majorVersion}/annotated-source", (err) -> throw err if err |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most minor thing ever ... I know that you didn't change anything here, but I got curious. I always thought ./node_modules/.bin/whatever
was the way to go when invoking "binaries" installed locally with npm. I guess it doesn't matter. :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great! Good job! 👍
Very nice. |
Hey guys, I think I have So there are now |
@jashkenas I’ve updated the code per your comment. Do you or @lydell have any other notes? |
I had some trouble with First, the terminal screen was cleared. Is that intended? Then, the following message appeared:
After that, I ended up in an endless loop of:
One line appears at a time, and then the screen is cleared before staring over again. Here's me trying
I'd expected Something similar happens for
And for
I'm on Ubuntu 16.04 if that helps. |
The clearing is intended. That’s how my Gulp version works. When tests fail, they quickly fill up the screen and often spill into several screenfuls; I found it convenient to be able to quickly scroll up to the first failed test, without needing to scan for when the previous batch of failed tests ended. I’ve only tested on OS X. Maybe |
I'm running Node.js 7.2. If you didn't change the implementation of the watching I guess everything is fine, since this PR isn't about fixing watch bugs. If you want to use chokidar I think that would be a good idea, though. Still, isn't it weird that |
A test in It shouldn’t be creating a file in I tested it in a Docker |
Nice! That fixed the infinite loop problem.
|
… we try to delete it
Such weirdness around files cross-platform. Okay, I added a check around the deletion of the REPL test history file. Now all good? |
I think we're all good now, because I suspect the following happens due to compiling and/or testing several times rapidly:
But, as you say, improving watch could be another PR. So, for me, it's OK to merge now :) |
cake release
task to cut a release.install
task.cake build:watch
andcake build:watch:harmony
tasks to build and test and rebuild on changes to the source or tests; based on https://github.com/GeoffreyBooth/coffeescript-gulp