Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Small content edits #2251

Merged
merged 1 commit into from
Oct 25, 2018
Merged

Small content edits #2251

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/api/last-run.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ sidebar_label: lastRun()

Retrieves the last time a task was successfully completed during the current running process. Most useful on subsequent task runs while a watcher is running.

When combined with `src()`, enables incremental builds to speed up your execution times by skipping files that haven't changed since the last successful task completion.
When combined with `src()`, enables incremental builds to speed up execution times by skipping files that haven't changed since the last successful task completion.

## Usage

Expand Down Expand Up @@ -64,7 +64,7 @@ While there are sensible defaults for the precision of timestamps, they can be r
* `lastRun(someTask, 100)` returns 1426000001100
* `lastRun(someTask, 1000)` returns 1426000001000

A file's [mtime stat][fs-stats-concepts] precision may vary depending on the node version and/or the file system used:
A file's [mtime stat][fs-stats-concepts] precision may vary depending on the node version and/or the file system used.


| platform | precision |
Expand Down