Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

msgpack.decode() not working for chrome >=60

See original GitHub issue

screenshot from 2017-08-14 12-06-56

It’s working fine for chrome versions, before 60. Also not working on latest firefox! Please do review decode() function.

Issue Analytics

State:
Created 6 years ago
Comments:21 (9 by maintainers)

Top GitHub Comments

1reaction

antlafargecommented, Aug 30, 2017

msgpack5.js and msgpack5.min.js in the dist directory are unchanged. And I have the same problem.

1reaction

antlafargecommented, Aug 28, 2017

Same bug, reproduced here in Chrome 60, Firefox 55 and Edge 40 : https://jsfiddle.net/antlafarge/wrjzt1zy/

Top Results From Across the Web

Developers - msgpack.decode() not working for chrome >=60 -

msgpack.decode() not working for chrome >=60. ... A msgpack v5 implementation for node.js, with extension points / msgpack.org[Node]. See More ...

MessagePack: It's like JSON. but fast and small.

MessagePack is an efficient binary serialization format. It lets you exchange data among multiple languages like JSON. But it's faster and smaller.

Preview MessagePack format in WebSocket Inspector

I tried working on this bug. I decoded the messagepack and converted it to JSON using the deserialize method present in msgpack.js file...

Msgpack5: A Msgpack V5 Implementation for Node.js and The ...

toString('hex')) // d5426161 console.log(decode(encode(a)) instanceof MyType) ... var level = require('level') , pack = msgpack() , db = level('foo', ...

Bug listing with status CONFIRMED as at 2022/12/26 10:46:31

There is no server at all: it only relies on end-users' machines. ... does not work with multiple lines" status:CONFIRMED resolution: severity:normal ...