Update AmplitudeJS start config

[erlanenazarov]

Question Checklist

• I updated Amplitude.js to the latest version
• I read the docs
• I searched for existing GitHub issues

Question Description

I am trying to use Amplitude JS on ReactJS and I have a few questions.
I have two ways to use Amplitude in my app:

• I'm initialize AmplitudeJS globally and assign instance to window object. If choose this way I can't access to callbacks config 'cuz Amplitude already initialized. So how can I add listeners to already initialized Amplitude instance?
• I'm initialize Amplitude directly in React component. If I choose this way I got a problem Amplitude continues play music even if React component was unmount. So how I should destroy AmplitudeJS instance on componentWillUnmount?

[Sun0fABeach]

I've got the same issue when using Amplitude inside a Vue component. Since there is no destroy method, I have to leave it initialized when destroying the component. I just call init again on the Amplitude instance once the component mounts again. This seems to work, but a duplicate init feels kinda dirty. Can someone confirm that this won't cause any issues? Anyways, it would be nice to have a clean destroy method.

[ampedweb]

I was looking for a clean destroy method too, quite suprised one doesn't exist!

I've got the same issue when using Amplitude inside a Vue component. Since there is no destroy method, I have to leave it initialized when destroying the component. I just call init again on the Amplitude instance once the component mounts again. This seems to work, but a duplicate init feels kinda dirty. Can someone confirm that this won't cause any issues? Anyways, it would be nice to have a clean destroy method.