Proposal: the delay option

[Fmajor]

I build a website with Nuxt.js, i have complicated backend models and it will take several seconds before the database is initialized and ready to work.
I run ava with the --watch option and will failed each time i update the source code (because the tests start immediately after i modify the source code before the database is ready)

Can we have a delay option to control the delay time after the source file are updated when we use the --watch option?

i want a CLI option --delay 5000 and the package.json config:

ava: {
  delay: 5000
}

to have a 5.0s delay time.

[sindresorhus]

I think a better and less fragile solution is for your code to wait for the database to be ready (detect it somehow).

[novemberborn]

You could do that detection in an asynchronous test.before(async () => { await startup() }) hook.

(I'm closing this issue for housekeeping purposes, but let's keep the conversation going.)

[Fmajor]

thanks, i have write anoter functiontestInitDone and put it into the before hook

anyway, i saw the delay option in other packages with the watch feature, maybe there are conditions that people must use this feature

[novemberborn]

I can see it being useful if the watcher picks up on files written by another process, and those files are written more slowly than it currently allows for. I don't recall anybody reporting such problems, though.

[jakobrosenberg]

A delay option like Rollup's buildDelay, could help prevent multiple triggers when multiple files are output to a dist folder.

[novemberborn]

@jakobrosenberg is this a problem you're encountering?

[jakobrosenberg]

@novemberborn, yes. especially for projects where dist files are written by different async functions.

An even better option would be something like, diskIdle: 200. This would take into account async file writes and sequential build steps like recreating a serviceworker manifest from the content of a dist folder.

[novemberborn]

@jakobrosenberg let's discuss here: #2702