decache | :shipit: Delete Cached node_modules useful when you need to "un-require" during testing for a fresh | Caching library

How is the file created? You probably just have a race condition with the file being created (which triggers the fs.watch event and reading of the file), then the JSON is written after a bit of processing, but it's already too late. Or the JSON is big and it takes time to write it all.

Two options for you:

• the process that creates the JSON should work in another directory (but on the same filesystem). Once the file is fully written out, move it to the directory. This way, you have an atomic change, and you know that when you receive the event the file is complete.

  An alternative is to write in the same directory, but rename once finished, and have a convention for what files are temporary or final (e.g. if the file is .xxxx.tmp ignore the event).

• or whenever you receive an event for a file (rename or change):

  • cancel any previously created timer for that file
  • create a new timer for that file
  • when the timer expires, actually read the file

As a rule of thumb, stubs should be set up per test, i.e. in beforeEach or it, not in before. Here they don't seem to contain per-test logic but they can, and in this case they won't work as expected with before. mocha-sinon should preferably be used to integrate Mocha with Sinon sandbox, so no afterEach is needed to restore stubs, this is done automatically.

Since verifySignature is export property and not the export itself, signatureMiddleware module may be left as is, but modules that use it should be de-cached and re-imported in tests where they are expected to use verifySignature. If the behaviour should be same for entire test suite, this should be performed in beforeEach as well. E.g. if these middlewares are used in app module directly, it's: