v0.1.2 — non-ASCII (UTF-8) fix

Fixed

• Non-ASCII characters no longer corrupt the socket read or shift OT positions. Overleaf's
  socket.io 0.9 transport UTF-8-encodes outgoing payloads at the application layer, so a
  character like an em-dash (—) arrived as 3 mojibake chars (â\x80\x94). That inflated its
  length and drifted every OT position after it, causing push to land edits on the wrong
  character and Overleaf to reject the batch. The read now reverses that framing (utf8Decode).

  Verified: an em-dash round-trips as a single character, and a push that inserts one — over a
  document already containing other non-ASCII text — reports verified match: yes.

npm install -g overleaf-review