geoffdutton / amplitude Goto Github PK

This is from the previous maintainer's issue from @harytkon:

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?

Hi,

lately, I'm getting this error while building (fail)

node_modules/amplitude/node_modules/axios/index.d.ts(62,38): error TS2304: Cannot find name 'ProgressEvent'.
node_modules/amplitude/node_modules/axios/index.d.ts(63,40): error TS2304: Cannot find name 'ProgressEvent'.

Getting this error when trying to track an event.

Here is the full error:

Unhandled Promise Rejection
{
"errorType": "Runtime.UnhandledPromiseRejection",
"errorMessage": "Error: Client network socket disconnected before secure TLS connection was established",
"reason": {
"errorType": "Error",
"errorMessage": "Client network socket disconnected before secure TLS connection was established",
"code": "ECONNRESET",
"path": null,
"host": "api.amplitude.com",
"port": 443,
"stack": [
"Error: Client network socket disconnected before secure TLS connection was established",
" at connResetException (internal/errors.js:570:14)",
" at TLSSocket.onConnectEnd (_tls_wrap.js:1361:19)",
" at Object.onceWrapper (events.js:299:28)",
" at TLSSocket.emit (events.js:215:7)",
" at endReadableNT (_stream_readable.js:1183:12)",
" at processTicksAndRejections (internal/process/task_queues.js:80:21)"
]
},
"promise": {},
"stack": [
"Runtime.UnhandledPromiseRejection: Error: Client network socket disconnected before secure TLS connection was established",
" at process. (/var/runtime/index.js:35:15)",
" at process.emit (events.js:210:5)",
" at processPromiseRejections (internal/process/promises.js:201:33)",
" at processTicksAndRejections (internal/process/task_queues.js:94:32)"
]
}

Will you add support to Typescript? I would really love to have it!

https://status.amplitude.com/

There has been a certificate chain problem on the amplitude API, they have a new API (api2.amplitude.com), can you update your library to use this for the time being?

After reviewing the README and the NodeJS module page, I couldn't find any documentation indicating that the API supports user mapping/aliasing (https://help.amplitude.com/hc/en-us/articles/360002750712#h_76557c8b-54cd-4e28-8c82-2f6778f65cd4). I just wanted to confirm that it doesn't support this?

I've been getting this a lot:

Request failed with status code 503

According to the Amplitude docs, a 503 "can be retried without any risk of duplicating an event": https://help.amplitude.com/hc/en-us/articles/360032842391-HTTP-API-V2

Would it be possible to automatically retry calls with a 503 response status?

Hi team,

How is this package licensed? Would it be possible to add a LICENSE file?

Thank you for maintaining this project!

I see that the library is using axios, does it support axios retry library?

The dependency superagent was updated from 5.2.1 to 5.2.2.

🚨 View failing branch.

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

superagent is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:

• CircleCI
• Travis CI
• Buildkite
• CodeShip
• Azure Pipelines
• TeamCity
• Buddy
• AppVeyor
  But Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.