[Bug] Analytics JS messageId generation not always unique (hash collision) about analytics-next HOT 2 CLOSED

@andrewloyola Thanks. This a good find. That's a big no-no.

Background: because of requirements around browser support, the simple uuid is not safe -- which is why hashing was added to begin with.

I think we're interested in ripping the band-aid off and removing the md5 dependency, and just doing:
https://github.com/segmentio/analytics-next/blob/master/packages/node/src/lib/get-message-id.ts

(Appending the current epoch date should add safety. Our thinking is that the odds that any given hash collision would happen at the same time, down to the ms, is much less (We haven't had any complaints yet on node)).

from analytics-next.

ah yes that makes sense, and glad there is already a pattern to do so. The epoch date solution should cover the cases we've seen at least. +1 support on band-aid ripping.

from analytics-next.