You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, jumpgen has a store object for preserving arbitrary data between runs. When combined with the changes array, you can manually determine which data in your store has been invalidated, allowing you to know which parts of your generator need to be rerun.
With a new API, we could make this less of a hassle.
Add task function that takes a name string and a callback.
When a task starts and ends, a "task:start" or "task:end" event is emitted with the task name.
Any paths watched from within a task's callback will only invalidate that task when changed.
When your generator reruns, some tasks may not rerun and instead will return a memoized result, if nothing they watched has changed.
Optionally, you can specify that a task's result should be stored in a filesystem cache, rather than kept in memory. (This feature won't exist in the initial implementation)
The text was updated successfully, but these errors were encountered:
Currently, jumpgen has a
store
object for preserving arbitrary data between runs. When combined with thechanges
array, you can manually determine which data in yourstore
has been invalidated, allowing you to know which parts of your generator need to be rerun.With a new API, we could make this less of a hassle.
task
function that takes aname
string and a callback."task:start"
or"task:end"
event is emitted with the task name.The text was updated successfully, but these errors were encountered: