I don't like that a browser extension version 1.5 requires monitoring tool with the same version. In fact, LR extension 1.5 fully compatible with 1.4 monitoring tool, but we still force users to update. Things get worse with third-party monitoring tools. We already have at least one — guard-livereload. I shouldn't have to do commits like this.
We should rely on LiveReload protocol version.
My plan:
api_version is the version of LiveReload protocol.
api_version might not match an extension version. We can change extension version, but keep api_version the same.
I don't like that a browser extension version 1.5 requires monitoring tool with the same version. In fact, LR extension 1.5 fully compatible with 1.4 monitoring tool, but we still force users to update. Things get worse with third-party monitoring tools. We already have at least one — guard-livereload. I shouldn't have to do commits like this.
We should rely on LiveReload protocol version.
My plan: