Liberty Rowland

I've gone a different way with this and begun implementing a parallel solution from the ground-up that does both serialization and parsing. https://github.com/ryan-rowland/binary-schema I'm writing the backlog via GitHub issues...

Thank you @kamalbennani for bringing this up, we're currently investigating this internally and I will update you once we've confirmed and created an internal ticket to address it.

Hi @JeremyShapiro, thanks for following up. We're currently working on some other big priorities, however, we'll be doing some planning in the coming weeks and I'll bring this up again...

Thanks @cesaric, I agree these should be enumerated. I've created a ticket internally that we will assign a priority to soon.

Hi @Shreets, have you tried using our [answerOnBridge](https://www.twilio.com/docs/voice/twiml/dial#answeronbridge) setting in your TwiML app? This setting separates ringing from answered and I believe should give you the specificity you're looking for....

Thanks @franzbecker , we'll look into this upgrade. Because this is a different package, we will have to do some extra testing to make sure all functionality is the same...

Thanks for the report! We don't officially support or test with Next.js, but I don't know of any reason why it shouldn't work. @burstWizard thanks for the resolution here; can...

Ahh, got it. Yes, this is unfortunate, because the Singleton pattern has been deprecated for a while and is only still included for backward compatibility. In the [Voice JS SDK...

Thanks for this suggestion @LuisPerez94, I will need to speak to our open source team here on the specifics of this.

Hi Adam, Thanks for the PR. I did leave some comments a few months ago, but haven't heard back in a while. Please let me know if you're still interested...