Potential memory leaks with event listeners

[k-ivan]

Thanks for the great plugin!

It seems to me that in the method for removing event handlers there is not enough removal for the keydown event.
https://github.com/kamranahmedse/driver.js/blob/master/src/events.ts#L118

[k-ivan]

And it’s not enough to delete events in this place, especially important for SPA project.
https://github.com/kamranahmedse/driver.js/blob/0889e01c809c93f261e321e80d65ee3b25d92387/src/events.ts#L101 - https://github.com/kamranahmedse/driver.js/blob/0889e01c809c93f261e321e80d65ee3b25d92387/src/events.ts#L113

All these events, each time the method drive() launched, multiply the number of handlers.

[k-ivan]

Maybe I'm missing something, but on the screen there are 3 states after calling the method (check with getEventListeners(document))

1. before the plugin works
2. first launch driver
3. re-launch driver(or prev|next click)

[k-ivan]

Hello @kamranahmedse !
I wanted to ask if you are still maintaining this wonderful plugin, could you consider my PR on this issue?

I would really like to solve this problem.

[capdiem]

Hello @kamranahmedse, I noticed that this issue has been around for some time now. Could you please provide an update or let us know if there are any plans to address this issue? Thank you!