Allow excluding certain files from cypress watch

[silbinarywolf]

Current behavior:

The seek-oss/css-modules-typescript-loader module generates *.d.ts files as part of the Webpack build. When running this alongside Cypress, it will get caught in an infinite loop.

Desired behavior:

1. Cypress offers config options to ignore certain files from being watched in cypress.json.
2. Cypress could perhaps track what files were changed during the initial Webpack build process and subsequently ignore them (ie. not reload) if those files are changed again.

I've also raised an issue here to solve the problem at the other end too:

• Using this alongside Cypress can cause an infinite loop due to Cypresses file watcher seek-oss/css-modules-typescript-loader#5

Steps to reproduce: (app code and test code)

• Pull down this repo (my feature-improvements branch): silbinarywolf/cypress-aurelia-unit-test@4db0f8b
• Run npm install
• Run cypress open and run the 'box-component.test.ts'
• You should notice that the tests pass and but the page just keeps reloading.

[kuceb]

Hi @silbinarywolf , you should be able to use the Preprocessor API to modify how cypress watches files and reloads

Does this help?

[silbinarywolf]

@bkucera If documentation can be added here alongside watchForFileChanges here that explains how to ignore certain files via the preprocessor API, that'd be good. The issue was more that it wasn't immediately obvious how I can just force Cypress to ignore a certain file from being changed.

I was looking for something to turn exclude files being watched in the configuration section of the documentation.

My specific problem has been solved* in the library I mentioned above so it's up to you guys how you want to educate users on this I guess! I'm happy for this to be closed at your discretion.

• I'm yet to pull it down and actually test it, but it looks like it should do the job

[kuceb]

@silbinarywolf Could you open up an issue here for the documentation changes? Feel free to leave more comments below if you have any future issues about this. Thanks!