-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
replacement solutions? #44
Comments
@chrisbutler : same over here. Can you share how you solved this? Which tactic did you end up using? |
PLUS one for keeping this package alive. I lost time playing around with FINALLY I installed THIS package here (yeah it is 2017) and I got it working blazing fast - BOTH on client and SERVER!!! Note that server has a slightly different api, as noted here #27. |
@thebarty i went down the same path hah. i have different apps using different solutions right now... i'd have to go back and look to tell you specifics |
this package just started breaking on me. it seems like segment may have changed their code so that its not compatible. just wasted a couple hours debugging this to find out that it seems like their code needs to use window.analytics and doesn't seem to be compatible with the modified snippet this package is using. anyone else having problems? |
actually I think my problem is actually related to switching to use ES6 imports. I made a patch that solved it for me but it's a bit hacky. |
I'm not sure this should be deprecated since there isn't a way to get analytics.js working client-side via NPM (at least not that I've found...)
I just wasted a few hours trying (and failing) with different npm packages... does anyone have a good way to easily replace this package's functionality?
The text was updated successfully, but these errors were encountered: