Conflict With Grok-Js

[lcharbon]

When the library grok-js is imported to an app with kafkajs the output of await producer.send() is an empty array.

See minimal example here.

In this example, if const grok = require('grok-js'); is uncommented kafkajs will stop working.

Issue submitted to grok-js here.

[JaapRood]

The only way I can see these two libraries conflict is if one of them mutates the environment, a global, altering the behaviour of some native functionality. A quick glance at the code of grok-js itself, I couldn't spot any, nor am I aware of the use of global in KafkaJS. More likely, I'd say, would be one of grok's dependencies being the culprit.

It'll be pretty hard to spot, which is exactly why the practice of mutating the environment shouldn't have passed code-review on this end. Good luck hunting it down, happy to help if you find anything more concrete!

[Nevon]

This is because gork-js depends on collections, which replaces Array.prototype.from with a version that doesn't work with iterables. See montagejs/collections/issues/169

This breaks KafkaJS because in this line we pass an iterable to Array.from, which returns an empty array with collections implementation.

Closing this, as it has nothing to do with KafkaJS.

[JaapRood]

This is because gork-js depends on collections, which replaces Array.prototype.from with a version that doesn't work with iterables.

🤦‍♀️