David Wells

Closing. Let me know if you still have issue or any additional context

You can conditionally enable/disable stuff https://getanalytics.io/conditional-loading/#enabling--disabling-plugins ```js routerListenerThingie((route) => { if (route === 'foo') { analytics.plugins.disable(['segment]) } }) ``` Or perhaps you can initialize another analytics instance without those plugins...

Axios is just making calls directly to segment https://github.com/segmentio/analytics-node/blob/master/index.js#L303 I don't think this security warning will have any impact on you. If you are just using segment in the browser...

`heartbeat` ticks every 3 sec and flushes any queued events https://github.com/DavidWells/analytics/blob/dca32cb95cbf8b38d36fcc866d21f9553f29ac24/packages/analytics-core/src/index.js#L982 `abort` should be a function there. I've tested this locally with another `identifyStart` plugin. Are you calling `abort` from...

Aha I see. We probably need a `noOp` function in heartbeat. Need to test this out ``` method({ payload: enrichedPayload, config: plugins[currentPlugin].config, instance, // NoOp on queue drain abort: ()...

> Why shouldn't the plugins called from heartbeat be abortable? Yeah probably. The heartbeat was initially setup for simple edge cases though ("Just queue events to fire when network resumes")....

Fixed in `[email protected]` Thanks for reporting this edge case

No plans on implementing this myself. Open to PRs though

To debug you gotta look at the DOM to verify that GA and Amplitude are loaded. Then, simulate the tracking call and verify the network requests are being made by...

Hello there. I'm not using mixpanel myself. Double check the network calls in the browser dev tools to ensure the values being sent are defined and not null