crookedneighbor / amplitude

A node wrapper for Amplitude analytics

amplitude

New Maintainer

This project is now maintained at https://github.com/geoffdutton/amplitude

amplitude's Issues

Remove dependency on babel

Remove nock dependency

Nock is a thorn in my side whenever I have to tweak something. Would be better to extract the superagent stuff into a request lib and then just stub the request in the tests.

Can't detect default data events

Hello!

Why the module can't detect this default data?
http://joxi.ru/DmBgQVLTNNREx2

If i using Javascript library or Android SDK for Amplitude, no problem at all, but if i am trying to use this node.js module i can't see that data.

why does it require a user ID to init?

i was looking at adding this to a server app

var amplitude = new Amplitude('api-token', { user_id: 'some-user-id' });

but with that requirement it seems I would have to track a list of amplitude objects for each user on the system, and reuse them?

since the server is handling lots of users obviously, this seems weird - is this because it's a client side SDK that you've wrapped (which assumes just one user for a session)

it would be much more convenient if we could just send trackEvent( userId, data )
and not have to track and reuse the correct amplitude instances per user in order to send events.

another way is to create (init) a new amplitude object every time I want to track an event, but that seems very wasteful/leaky too.

Am I missing something in how to use this wrapper?

An in-range update of sinon is breaking the build 🚨

The devDependency sinon was updated from 7.2.4 to 7.2.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Commits

The new version differs by 8 commits.

• 8b8bddd Update docs/changelog.md and set new release id in docs/_config.yml
• 33f0b67 Add release documentation for v7.2.5
• 2b4bc7d 7.2.5
• fb54e29 Update CHANGELOG.md and AUTHORS for new release
• 8ac68f3 Upgrade mochify to latest
• add43e3 Upgrade @sinonjs/samsam to latest
• d0c073c don't call extends.nonEnum in spy.resetHistory (#1984)
• f99e2ef Use stable Chrome in Circle

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Open to taking over as a maintainer

My company uses this pretty extensively, so I'd be happy to spend time to keep it updated and moving forward.

@crookedneighbor Let me know what you think/have questions/etc.

Support connection keep-alive

It can be useful to pass an HttpsAgent to the constructor to control connection keep-alive.
It can significantly reduce the time for each request, especially if not sending in batches.

Does it make sense to you adding this feature?

An in-range update of publish-please is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.4.0 of publish-please was just published.

Branch	Build failing 🚨
Dependency	publish-please
Current Version	2.3.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

publish-please is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 1 commits.

• 6e5bea1 Add support for a custom publishing command, fix postpublish script (#54)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Support for Amplitude HTTP API v2

Amplitude deprecates HTTP API v1.
https://help.amplitude.com/hc/en-us/articles/360032842391-HTTP-API-V2

Any plans to provide support for HTTP API v2?

Publish latest version to NPM

Blade, any way you could publish a new version of the package to NPM with an updated package.json for superagent? The currently published version still references ^3.3.1 which produces the follow warning on install:

npm WARN deprecated [email protected]: Please note that v5.0.1+ of superagent removes User-Agent header by default, therefore you may need to add it yourself (e.g. GitHub blocks requests without a User-Agent header). This notice will go away with v5.0.2+ once it is released.

The one in GitHub references ^5.0.7.

An in-range update of publish-please is breaking the build 🚨

The devDependency publish-please was updated from 5.4.3 to 5.5.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

publish-please is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v5.5.0

Changelog: https://github.com/inikulin/publish-please/blob/master/CHANGELOG.md#550---2019-07-01

Commits

The new version differs by 19 commits.

• f86f495 doc(git-tag-check): apply @motin suggestion
• 62d3ef4 doc(git-tag-check): update README
• d85a4ab test(publish-with-publish-please): fix test on CI with npm version 6.9.2
• b487d88 test(publish-with-publish-please): try fix test on CI with npm version 6.9.2
• 0584c15 test(publish-with-publish-please): try fix test on CI with npm version 6.9.2
• 66c6bea test(vulnerability-check): adapt test due to changes in results from npm audit
• 545d989 test(vulnerability-check): adapt test due to changes in results from npm audit
• d64fd5f fix(vulnerability-check): remove duplicated output
• 1247566 test(vulnerability-check): adapt test due to changes in results from npm audit
• 0738a3e test(vulnerability-check): adapt test due to changes in results from npm audit
• fa2ba9e test(vulnerability-check): adapt test due to changes in results from npm audit
• a53a537 test(vulnerability-check): adapt test due to changes in results from npm audit
• 2c0ab49 test(vulnerability-check): adapt test due to changes in results from npm audit
• 77463c9 test(vulnerability-check): add test due to changes in results from npm audit
• ff095a6 test(vulnerability-check): adapt test due to changes in results from npm audit

There are 19 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Return empty

My code return empty, when I use the segmentation return data,

amplitude.track({
event_type: 'Enter Project',
}).then(function (result) {

    console.log(result);
        return response.status(200).json(result);

    }).catch(function (error) {
    return response.status(400).json(error);
});

Ca I pass user_id in eventSegmentation?

track() uses POST, but puts all data in the query string

According to Amplitude they don't have a limit on the data you can pass....but if all properties are in the query string you can hit a limit.

Is there a reason the data isn't sent as POST fields?

An in-range update of sinon is breaking the build 🚨

The devDependency sinon was updated from 7.3.0 to 7.3.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Commits

The new version differs by 6 commits.

• 3812a7d Update docs/changelog.md and set new release id in docs/_config.yml
• 93bef55 Add release documentation for v7.3.1
• e02c192 7.3.1
• 8ee1d35 Update CHANGELOG.md and AUTHORS for new release
• bc53d82 Fix security issues
• 1a09166 Update @sinonjs/samsam to v3.3.1

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of mocha is breaking the build 🚨

The devDependency mocha was updated from 6.1.4 to 6.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v6.2.0

6.2.0 / 2019-07-18

🎉 Enhancements

• #3827: Do not fork child-process if no Node flags are present (@boneskull)
• #3725: Base reporter store ref to console.log, see mocha/wiki (@craigtaub)

🐛 Fixes

• #3942: Fix "No test files found" Error when file is passed via --file (@gabegorelick)
• #3914: Modify Mocha constructor to accept options global or globals (@pascalpp)
• #3894: Fix parsing of config files with _mocha binary (@juergba)
• #3834: Fix CLI parsing with default values (@boneskull, @juergba)
• #3831: Fix --timeout/--slow string values and duplicate arguments (@boneskull, @juergba)

📖 Documentation

• #3906: Document option to define custom report name for XUnit reporter (@pkuczynski)
• #3889: Adds doc links for mocha-examples (@craigtaub)
• #3887: Fix broken links (@toyjhlee)
• #3841: Fix anchors to configuration section (@trescube)

🔍 Coverage

• #3915, #3929: Increase tests coverage for --watch options (@geigerzaehler)

🔩 Other

• #3953: Collect test files later, prepares improvements to the --watch mode behavior (@geigerzaehler)
• #3939: Upgrade for npm audit (@boneskull)
• #3930: Extract runWatch into separate module (@geigerzaehler)
• #3922: Add mocha.min.js file to stacktrace filter (@brian-lagerman)
• #3919: Update CI config files to use Node-12.x (@plroebuck)
• #3892: Rework reporter tests (@plroebuck)
• #3872: Rename --exclude to --ignore and create alias (@boneskull)
• #3963: Hide stacktrace when cli args are missing (@outsideris)
• #3956: Do not redeclare variable in docs array example (@DanielRuf)
• #3957: Remove duplicate line-height property in mocha.css (@DanielRuf)
• #3960: Don't re-initialize grep option on watch re-run (@geigerzaehler)

Commits

The new version differs by 39 commits.

• bd47776 Release v6.2.0
• cc595af update CHANGELOG.md for v6.2.0 [ci skip]
• 59d70ee fix: remove duplicate line-height property (#3957)
• f77cac4 fix: do not redeclare variable (#3956)
• 6201e42 Hide stacktrace when cli args are missing (#3963)
• 88f45d5 Don't re-initialize grep option on watch re-run (#3960)
• 5d4dd98 Fix No Files error when file is passed via --files (#3942)
• 15b96af Collect test files later (#3953)
• ccee5f1 Base reporter store ref to console.log (#3725)
• 47318a7 update @mocha/contributors to v1.0.4 (#3944)
• c903147 More, improved integration tests for watching (#3929)
• e341ea4 Update CI config files to use Node-12.x (#3919)
• 3064d25 update @mocha/docdash to v2.1.1 (#3945)
• 9ea45e7 do not fork if no node flags present (#3827)
• d02a096 modify Mocha constructor to accept options.global or options.globals (#3914)

There are 39 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Documentation update

Great work and very useful, thank you!

The Amplitude identify API supports operations like $add, $append, etc.
Looks like it's possible to use the library for these operations also.

    var event = {
        userId: userid,
        userProperties: {
            $set: {
                firstName: 'firstName',
                lastName: 'lastName'
            },
            $add: { counter: 1 }
        }
    };
    amplitude.identify(event);

Add method to hit identity route in Amplitude API

An in-range update of mocha is breaking the build 🚨

The devDependency mocha was updated from 6.0.2 to 6.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v6.1.0

6.1.0 / 2019-04-07

🔒 Security Fixes

• #3845: Update dependency "js-yaml" to v3.13.0 per npm security advisory (@plroebuck)

🎉 Enhancements

• #3766: Make reporter constructor support optional options parameter (@plroebuck)
• #3760: Add support for config files with .jsonc extension (@sstephant)

📠 Deprecations

These are soft-deprecated, and will emit a warning upon use. Support will be removed in (likely) the next major version of Mocha:

• #3719: Deprecate this.skip() for "after all" hooks (@juergba)

🐛 Fixes

• #3829: Use cwd-relative pathname to load config file (@plroebuck)
• #3745: Fix async calls of this.skip() in "before each" hooks (@juergba)
• #3669: Enable --allow-uncaught for uncaught exceptions thrown inside hooks (@givanse)

and some regressions:

• #3848: Fix Suite cloning by copying root property (@fatso83)
• #3816: Guard against undefined timeout option (@boneskull)
• #3814: Update "yargs" in order to avoid deprecation message (@boneskull)
• #3788: Fix support for multiple node flags (@aginzberg)

📖 Documentation

• mochajs/mocha-examples: New repository of working examples of common configurations using mocha (@craigtaub)
• #3850: Remove pound icon showing on header hover on docs (@jd2rogers2)
• #3812: Add autoprefixer to documentation page CSS (@Munter)
• #3811: Update doc examples "tests.html" (@DavidLi119)
• #3807: Mocha website HTML tweaks (@plroebuck)
• #3793: Update config file example ".mocharc.yml" (@cspotcode)

🔩 Other

• #3830: Replace dependency "findup-sync" with "find-up" for faster startup (@cspotcode)
• #3799: Update devDependencies to fix many npm vulnerabilities (@XhmikosR)

Commits

The new version differs by 28 commits.

• f4fc95a Release v6.1.0
• bd29dbd update CHANGELOG for v6.1.0 [ci skip]
• aaf2b72 Use cwd-relative pathname to load config file (#3829)
• b079d24 upgrade deps as per npm audit fix; closes #3854
• e87c689 Deprecate this.skip() for "after all" hooks (#3719)
• 81cfa90 Copy Suite property "root" when cloning; closes #3847 (#3848)
• 8aa2fc4 Fix issue 3714, hide pound icon showing on hover header on docs page (#3850)
• 586bf78 Update JS-YAML to address security issue (#3845)
• d1024a3 Update doc examples "tests.html" (#3811)
• 1d570e0 Delete "/docs/example/chai.js"
• ade8b90 runner.js: "self.test" undefined in Browser (#3835)
• 0098147 Replace findup-sync with find-up for faster startup (#3830)
• d5ba121 Remove "package" flag from sample config file because it can only be passes as CLI arg (#3793)
• a3089ad update package-lock
• 75430ec Upgrade yargs-parser dependency to avoid loading 2 copies of yargs

There are 28 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of mocha is breaking the build 🚨

Version 3.4.0 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.3.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

v3.4.0

Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.

This week's highlights:

• allowUncaught added to commandline as --allow-uncaught (and bugfixed)
• warning-related Node flags

🎉 Enhancements

• #2793, #2697: add --allowUncaught to Node.js (@lrowe)
• #2733: Add --no-warnings and --trace-warnings flags (@sonicdoe)

🐛 Fixes

• #2793, #2697: fix broken allowUncaught (@lrowe)

🔩 Other

• #2778: Add license report and scan status (@xizhao)
• #2794: no special case for macOS running Karma locally (@boneskull)
• #2795: reverts use of semistandard directly ([#2648]) (@boneskull)

Commits

The new version differs by 9 commits0.

• 7554b31 Add Changelog for v3.4.0
• 9f7f7ed Add --trace-warnings flag
• 92561c8 Add --no-warnings flag
• ceee976 lint test/integration/fixtures/simple-reporter.js
• dcfc094 Revert "use semistandard directly"
• 93392dd no special case for macOS running Karma locally
• 4d1d91d --allow-uncaught cli option
• fb1e083 fix allowUncaught in browser
• 4ed3fc5 Add license report and scan status

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Remove q dependency