Closed kazuho closed 10 years ago
As can be seen in the following log, jsx-with-server does not check the version of the backend it connects to, leading to unexpected behavior from users' view point (under an enviroment in which multiple versions of JSX are installed).
jsx-with-server
$ jsx --version 0.9.84 (2014-03-25 11:22:27 +0900; 1e07252cc54a2d7c6b4ab95268995c6656833a80) $ bin/jsx --version 0.9.84 (2014-04-08 18:03:58 +0900; 9288c866ba4e23e2d2fcb7e491270f6a1dd9ca92) $ jsx-with-server --version 0.9.84 (2014-04-08 18:03:58 +0900; 9288c866ba4e23e2d2fcb7e491270f6a1dd9ca92) $ bin/jsx-with-server --version 0.9.84 (2014-04-08 18:03:58 +0900; 9288c866ba4e23e2d2fcb7e491270f6a1dd9ca92) # <- should be 1e07252
might be (or might not be) the cause of #308
not a issue any more now that the server has been abolished in #318
As can be seen in the following log,
jsx-with-server
does not check the version of the backend it connects to, leading to unexpected behavior from users' view point (under an enviroment in which multiple versions of JSX are installed).