Skip to content
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

Open
chrisbutler opened this issue Oct 18, 2016 · 5 comments
Open

replacement solutions? #44

chrisbutler opened this issue Oct 18, 2016 · 5 comments

Comments

@chrisbutler
Copy link
Contributor

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?

@thebarty
Copy link

thebarty commented Aug 5, 2017

@chrisbutler : same over here. Can you share how you solved this? Which tactic did you end up using?

@thebarty
Copy link

thebarty commented Aug 5, 2017

PLUS one for keeping this package alive.

I lost time playing around with okgrow:analytics, which does NOT have server-support,
and then I lost time by reading the "deprecated"-message in this package and searching for an npm for analytics.js on the client, which does NOT seem to exist.

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.

@chrisbutler
Copy link
Contributor Author

@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

@hexsprite
Copy link

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?

@hexsprite
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants