@parcel/watcher wasm backend prevents bumping version

[alshdavid]

Hi all, working on bumping the @parcel/watcher version and found that the commit adding the wasm backend breaks the cache integration tests in Parcel.

The watcher still works fine in the real world, it's just that versions 2.3.0 and above break the integration test suite. We specify ^2.x.x in the Parcel monorepo which is pegged to 2.2.0 in the lock file - however consumers will get a newer version (because they don't have the same lock file). So consumers are installing a version of @parcel/watcher that breaks integration tests (though works in the real world).

Example breaking test:

1) cache
       compression
         should invalidate when updating a compressor plugin:

      AssertionError [ERR_ASSERTION]: Expected values to be loosely deep-equal:

[
  'index.js',
  'index.js.abc',
  'index.js.map'
]

should loosely deep-equal

[
  'index.js',
  'index.js.abc',
  'index.js.def',
  'index.js.map'
]

Working on a fix for that, please let me know if you have any suggestions 🙏
Is it safe for the tests to be updated?

Thanks