xojs
xo.config.ts, AVA watch mode and VSCode
When using an xo.config.ts file, and editing in VSCode with AVA's watch mode running and the XO extension installed, there is a brief window where xo.config.mjs files exist and are then deleted. This causes AVA to rerun all tests.
Is this expected behavior somewhere between XO and the VSCode extension? If it's unavoidable, should this be documented within XO, or AVA? Should AVA's watch mode always ignore XO and ESLint configuration files?
Its part of cosmiconfig loading - we should potentially document this since it might trip up other file watching tools.
https://github.com/cosmiconfig/cosmiconfig/blob/main/src/loaders.ts#L118
OK, that makes sense.
In your estimation, should AVA ignore *.config.* changes? We don't have a way for these hardcoded ignore patterns to be overruled.
hmm it might be good default behavior, but I think I can imagine a scenario where you have a config stub or fixture that you do want to watch, so not being able to override it might be a little problematic.
Do you expect these anywhere other than the project root? Or next to a package.json?