-
Notifications
You must be signed in to change notification settings - Fork 152
Closed
Description
Recently while doing some npm installs we noticed a significant break in our dependencies. Unfortunately our versions require protobufjs@2.2.1 - which then require bytebuffer@>=2.2 <3 - which then requires long@latest.
This appears to be a breaking change (rightly so, our old version of long was using 1.2 and the new one is 2.0) - but we don't have control over that per say. Any ideas on how to update bytebuffer to a version that uses the working long 1.2? Or is there something we need to change on our end?
What we noticed was:
Object function (low, high, unsigned) {
/**
* The low 32 bits as a signed value.
* @type {number}
* @expose
*/
this.low = low|0;
/**
* The high 32 bits as a signed value.
* @type {number}
* @expose
*/
this.high = high|0;
/**
* Whether unsigned or not.
* @type {boolean}
* @expose
*/
this.unsigned = !!unsigned;
} has no method 'from28Bits'