Closed GravityRZ closed 4 years ago
@GravityRZ That's on me. I was starting to work on locks and accidentally injected part of the code into the last update. I've put in a pull request to @andrei-tatar to fix it.
ok thanks. nothing broken as far as i can see so take your time
didn't notice this... I usually install with npm install
0.0.28
published with the fix.
tested it message was still there after upgrade(probably the old message) after restart everything ok
everything seems to work but i got this error after upgrade from 0.0.24 to 0.0.27