yourtion/node-qq-mta-sdk

Node.js SDK for QQ MTA 腾讯移动统计数据接口API Node.js SDK

qq-mta

Node.js SDK for QQ MTA (Mobile Tencent Analytics) 腾讯移动统计数据接口API Node.js SDK

安装使用使用

$ npm install qq-mta --save

const MTA = require('qq-mta');

const client = new MTA({
  appId: 'YOUR_APP_ID',
  appKey: 'YOUR_KEY',
  timeout: 30000, // 可选参数，单位：ms
});

接口

接口详细参数参考文档 腾讯移动分析 - 数据接口 :

• 应用基本指标 (离线数据) userBasicOffline(idx, start, end)
• 应用基本指标 (实时数据) userBasicRealtime(idx, start, end)
• 终端设备数据 terminal(idx, ty, start, end)
• 用户行为数据 (DAU、WAU、MAU) active(idx, start, end)
• 用户行为数据 (使用时长、访问页面) usage(idx, start, end)
• 用户行为数据 (使用频率) usageFreq(idx, start, end)
• 开发支持数据 (错误次数、错误覆盖人数) crash(idx, start, end)
• 开发支持数据 (环境数据) crashEnv(idx, ty, start, end)
• 开发支持数据 (崩溃列表) crashList(idx, errTy, start, end)

node-qq-mta-sdk's Issues

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

Version 3.19.0 of eslint just got published.

Branch	Build failing 🚨
Dependency	eslint
Current Version	3.18.0
Type	devDependency

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

As eslint 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

• ✅ coverage/coveralls First build on greenkeeper/eslint-3.19.0 at 94.059% Details

Release Notes

v3.19.0

• e09132f Fix: no-extra-parens false positive with exports and object literals (#8359) (Teddy Katz)
• 91baed4 Update: allow custom messages in no-restricted-syntax (fixes #8298) (#8357) (Vitor Balocco)
• 35c93e6 Fix: prevent space-before-function-paren from checking type annotations (#8349) (Teddy Katz)
• 3342e9f Fix: don't modify operator precedence in operator-assignment autofixer (#8358) (Teddy Katz)
• f88375f Docs: clarify that no-unsafe-negation is in eslint:recommended (#8371) (Teddy Katz)
• 02f0d27 Docs: Add soda0289 to Development Team (#8367) (Kai Cataldo)
• 155424c Fix: ignore empty path in patterns (fixes #8362) (#8364) (alberto)
• 27616a8 Fix: prefer-const false positive with object spread (fixes #8187) (#8297) (Vitor Balocco)
• 8569a90 Docs: add note about git's linebreak handling to linebreak-style docs (#8361) (Teddy Katz)
• 5878593 Chore: fix invalid syntax in no-param-reassign test (#8360) (Teddy Katz)
• 1b1046b Fix: don't classify plugins that throw errors as "missing" (fixes #6874) (#8323) (Teddy Katz)
• 29f4ba5 Fix: no-useless-computed-key invalid autofix for getters and setters (#8335) (Teddy Katz)
• 0541eaf Fix: no-implicit-coercion invalid autofix with consecutive identifiers (#8340) (Teddy Katz)
• 41b9786 Fix: no-extra-parens false positive with objects following arrows (#8339) (Teddy Katz)
• 3146167 Fix: eslint.verify should not mutate config argument (fixes #8329) (#8334) (alberto)
• 927de90 Fix: dot-notation autofix produces invalid syntax for integer properties (#8332) (Teddy Katz)
• a9d1bea Fix: comma-style autofix produces errors on parenthesized elements (#8331) (Teddy Katz)
• d52173f Fix: don't generate invalid options in config-rule (#8326) (Teddy Katz)
• 6eda3b5 Fix: no-extra-parens invalid autofix in for-of statements (#8337) (Teddy Katz)
• 6c819d8 Fix: dot-notation autofix produces errors on parenthesized computed keys (#8330) (Teddy Katz)
• 2d883d7 Fix: object-shorthand autofix produces errors on parenthesized functions (#8328) (Teddy Katz)
• cd9b774 Fix: quotes false positive with backtick option in method names (#8327) (Teddy Katz)
• d064ba2 Fix: no-else-return false positive for ifs in single-statement position (#8338) (Teddy Katz)
• 6a718ba Chore: enable max-statements-per-line on ESLint codebase (#8321) (Teddy Katz)
• 614b62e Chore: update sinon calls to deprecated API. (#8310) (alberto)
• 0491572 Chore: use precalculated counts in codeframe formatter (#8296) (Vitor Balocco)
• 8733e6a Chore: Fix incorrect error location properties in tests (#8307) (alberto)
• c4ffb49 Chore: Fix typos in test option assertions (#8305) (Teddy Katz)
• 79a97cb Upgrade: devDependencies (#8303) (alberto)
• e4da200 Upgrade: Mocha to 3.2.0 (#8299) (Ilya Volodin)
• 2f144ca Fix: operator-assignment autofix errors with parentheses (fixes #8293) (#8294) (Teddy Katz)
• 7521cd5 Chore: update token logic in rules to use ast-utils (#8288) (Teddy Katz)
• 9b509ce Chore: refactor space-before-function-paren rule (#8284) (Teddy Katz)
• ddc6350 Fix: no-param-reassign false positive on destructuring (fixes #8279) (#8281) (Teddy Katz)
• f8176b3 Chore: improve test coverage for node-event-generator (#8287) (Teddy Katz)
• 602e9c2 Docs: fix incorrect selector examples (#8278) (Teddy Katz)

Commits

The new version differs by 38 commits .

• 421aab4 3.19.0
• 26a4dd5 Build: changelog update for 3.19.0
• e09132f Fix: no-extra-parens false positive with exports and object literals (#8359)
• 91baed4 Update: allow custom messages in no-restricted-syntax (fixes #8298) (#8357)
• 35c93e6 Fix: prevent space-before-function-paren from checking type annotations (#8349)
• 3342e9f Fix: don't modify operator precedence in operator-assignment autofixer (#8358)
• f88375f Docs: clarify that no-unsafe-negation is in eslint:recommended (#8371)
• 02f0d27 Docs: Add soda0289 to Development Team (#8367)
• 155424c Fix: ignore empty path in patterns (fixes #8362) (#8364)
• 27616a8 Fix: prefer-const false positive with object spread (fixes #8187) (#8297)
• 8569a90 Docs: add note about git's linebreak handling to linebreak-style docs (#8361)
• 5878593 Chore: fix invalid syntax in no-param-reassign test (#8360)
• 1b1046b Fix: don't classify plugins that throw errors as "missing" (fixes #6874) (#8323)
• 29f4ba5 Fix: no-useless-computed-key invalid autofix for getters and setters (#8335)
• 0541eaf Fix: no-implicit-coercion invalid autofix with consecutive identifiers (#8340)

There are 38 commits in total. 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 🌴

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

Version 2.6.4 of debug just got published.

Branch	Build failing 🚨
Dependency	debug
Current Version	2.6.3
Type	dependency

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

As debug is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ coverage/coveralls Coverage pending from Coveralls.io Details

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

Commits

The new version differs by 6 commits .

• f311b10 release 2.6.4
• 1f01b70 Fix bug that would occure if process.env.DEBUG is a non-string value. (#444)
• 2f3ebf4 Update CHANGELOG.md
• f5ae332 Update CHANGELOG.md
• 9742c5f chore(): ignore bower.json in npm installations. (#437)
• 27d93a3 update "debug" to v0.7.3

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 🌴

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

Version 2.13.3 of coveralls just got published.

Branch	Build failing 🚨
Dependency	coveralls
Current Version	2.13.2
Type	devDependency

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

As coveralls 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

• ❌ coverage/coveralls Coverage pending from Coveralls.io 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 ahead by 1, behind by 2.

• b2a86d6 legacy 2.x version branch for node <= 4.x

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 🌴

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

Version 4.5.0 of eslint just got published.

Branch	Build failing 🚨
Dependency	eslint
Current Version	4.4.1
Type	devDependency

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

As eslint 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
• ✅ coverage/coveralls First build on greenkeeper/eslint-4.5.0 at 95.146% Details

---

Release Notes

v4.5.0

• decdd2c Update: allow arbitrary nodes to be ignored in indent (fixes #8594) (#9105) (Teddy Katz)
• 79062f3 Update: fix indentation of multiline new.target expressions (#9116) (Teddy Katz)
• d00e24f Upgrade: chalk to 2.x release (#9115) (Stephen Edgar)
• 6ef734a Docs: add missing word in processor documentation (#9106) (Teddy Katz)
• a4f53ba Fix: Include files with no messages in junit results (#9093) (#9094) (Sean DuBois)
• 1d6a9c0 Chore: enable eslint-plugin/test-case-shorthand-strings (#9067) (薛定谔的猫)
• f8add8f Fix: don't autofix with linter.verifyAndFix when fix: false is used (#9098) (Teddy Katz)
• 77bcee4 Docs: update instructions for adding TSC members (#9086) (Teddy Katz)
• bd09cd5 Update: avoid requiring NaN spaces of indentation (fixes #9083) (#9085) (Teddy Katz)
• c93a853 Chore: Remove extra space in blogpost template (#9088) (Kai Cataldo)

Commits

The new version differs by 12 commits.

• ff8c4bb 4.5.0
• 480bbee Build: changelog update for 4.5.0
• decdd2c Update: allow arbitrary nodes to be ignored in indent (fixes #8594) (#9105)
• 79062f3 Update: fix indentation of multiline new.target expressions (#9116)
• d00e24f Upgrade: chalk to 2.x release (#9115)
• 6ef734a Docs: add missing word in processor documentation (#9106)
• a4f53ba Fix: Include files with no messages in junit results (#9093) (#9094)
• 1d6a9c0 Chore: enable eslint-plugin/test-case-shorthand-strings (#9067)
• f8add8f Fix: don't autofix with linter.verifyAndFix when fix: false is used (#9098)
• 77bcee4 Docs: update instructions for adding TSC members (#9086)
• bd09cd5 Update: avoid requiring NaN spaces of indentation (fixes #9083) (#9085)
• c93a853 Chore: Remove extra space in blogpost template (#9088)

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 🌴

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

Version 3.5.2 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.5.1
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
• ✅ coverage/coveralls First build on greenkeeper/mocha-3.5.2 at 95.146% Details

---

Release Notes

v3.5.2

3.5.2 / 2017-09-10

🐛 Fixes

• #3001: Fix AMD-related failures first appearing in v3.5.1 (@boneskull)

Commits

The new version differs by 5 commits.

• 72622ab Release v3.5.2
• ac4c39f fix version in CHANGELOG.md [ci skip]
• f06d969 update CHANGELOG for 3.5.2 [ci skip]
• 9a3ddeb fix AMD bundle by hacking around check in he module; closes #3000
• 337d317 fix broken links in CHANGELOG.md [ci skip]

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 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

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 request is breaking the build 🚨

Version 2.82.0 of request just got published.

Branch	Build failing 🚨
Dependency	request
Current Version	2.81.0
Type	dependency

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

request is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

• ❌ coverage/coveralls Coverage pending from Coveralls.io Details
• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 27 commits.

• 0ab5c36 2.82.0
• ffdf0d3 Updating deps.
• 4386836 Merge branch 'master' of github.com:request/request
• 1527407 Merge pull request #2703 from ryysud/add-nodejs-v8-to-travis
• 3afcbf8 Merge branch 'master' of github.com:request/request
• 479143d Update of hawk and qs to latest version (#2751)
• 169be11 Add Node.js v8 to Travis CI
• 643c43a Fixed some text in README.md (#2658)
• e8fca51 chore(package): update aws-sign2 to version 0.7.0 (#2635)
• e999203 Update README to simplify & update convenience methods (#2641)
• 6f286c8 lint fix, PR from pre-standard was merged with passing tests
• a765593 Add convenience method for HTTP OPTIONS (#2541)
• 52d6945 Add promise support section to README (#2605)
• b12a624 refactor(lint): replace eslint with standard (#2579)
• 29a0b17 Merge pull request #2598 from request/greenkeeper-codecov-2.0.2

There are 27 commits in total.

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 🌴

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 could not complete due to an error 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 🌴

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

Version 4.4.1 of eslint just got published.

Branch	Build failing 🚨
Dependency	eslint
Current Version	4.4.0
Type	devDependency

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

As eslint 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
• ✅ coverage/coveralls First build on greenkeeper/eslint-4.4.1 at 95.146% Details

---

Release Notes

v4.4.1

• ec93614 Fix: no-multi-spaces to avoid reporting consecutive tabs (fixes #9079) (#9087) (Teddy Katz)

Commits

The new version differs by 3 commits.

• 0d9da6d 4.4.1
• 1ea9a6c Build: changelog update for 4.4.1
• ec93614 Fix: no-multi-spaces to avoid reporting consecutive tabs (fixes #9079) (#9087)

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 🌴

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

Version 2.13.1 of coveralls just got published.

Branch	Build failing 🚨
Dependency	coveralls
Current Version	2.13.0
Type	devDependency

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

As coveralls 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 could not complete due to an error [Details](https://travis-ci.org/yourtion/node-qq-mta-sdk/builds/226591500)

---

Commits

The new version differs by 1 commits0.

• b9032a1 better Jenkins detection

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 🌴

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

Version 2.13.0 of coveralls just got published.

Branch	Build failing 🚨
Dependency	coveralls
Current Version	2.12.0
Type	devDependency

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

As coveralls 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 could not complete due to an error Details

Commits

The new version differs by 4 commits .

• 2821200 version bump
• ef7e811 Parse commit from packed refs if not available in refs dir. (#163)
• e476964 Merge pull request #162 from evanjbowling/patch-1
• 63a7f92 Update README.md

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 🌴

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

Version 3.2.0 of debug was just published.

Branch	Build failing 🚨
Dependency	debug
Current Version	3.1.0
Type	dependency

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

debug 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.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
• ✅ coverage/coveralls: First build on greenkeeper/debug-3.2.0 at 95.146% (Details).

---

Release Notes

3.2.0

A long-awaited release to debug is available now: 3.2.0.

Due to the delay in release and the number of changes made (including bumping dependencies in order to mitigate vulnerabilities), it is highly recommended maintainers update to the latest package version and test thoroughly.

---

Minor Changes

• bump vulnerable packages: 853853f
• Fix nwjs support (#569): 207a6a2
• add instance extends feature (#524): e43e5fe
• Add TVMLKit support (#579): 02b9ea9

Patches

• move to XO (closes #397): ba8a424
• clean up builds: 3ca2331
• remove needless command aliases in makefile: 9f4f8f5
• no longer checking for BROWSER=1: 623c08e
• fix tests: 57cde56
• clean up makefile: 62822f1
• fix tests: 833b6f8
• add .editorconfig: 2d2509e
• add yarn-error.log to .gitignore: 7e1d5d9
• add Node.js 10, remove Node.js 4 (#583): 05b0ceb
• Improve usability of Windows notes w/ examples for prompts & npm script (#577): 1ad1e4a
• Drop usage of chrome.storage (or make the storage backend pluggable): 71d2aa7
• Detect 'process' package: 225c66f
• Update ms to 2.1.1 (#539): 22f9932
• Update .npmignore (#527): a5ca7a2
• fix colors with supports-color@5: 285dfe1
• Document enable() (#517): ab5083f
• refactor to make the common code be a setup function (#507): 7116906
• Simplify and improve: da51af8

Credits

Huge thanks to @DanielRuf, @EirikBirkeland, @KyleStay, @Qix-, @abenhamdine, @alexey-pelykh, @DiegoRBaquero, @febbraro, @kwolfy, and @TooTallNate for their help!

Commits

The new version differs by 25 commits.

• dec4b15 3.2.0
• 3ca2331 clean up builds
• 9f4f8f5 remove needless command aliases in makefile
• 623c08e no longer checking for BROWSER=1
• 57cde56 fix tests
• 62822f1 clean up makefile
• 833b6f8 fix tests
• ba8a424 move to XO (closes #397)
• 2d2509e add .editorconfig
• 853853f bump vulnerable packages
• 7e1d5d9 add yarn-error.log to .gitignore
• e43e5fe add instance extends feature (#524)
• 207a6a2 Fix nwjs support (#569)
• 05b0ceb add Node.js 10, remove Node.js 4 (#583)
• 02b9ea9 Add TVMLKit support (#579)

There are 25 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 debug is breaking the build 🚨

Version 2.6.8 of debug just got published.

Branch	Build failing 🚨
Dependency	debug
Current Version	2.6.7
Type	dependency

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

debug is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

• ❌ coverage/coveralls Coverage pending from Coveralls.io Details
• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 2 commits.

• 52e1f21 Release 2.6.8
• 2482e08 Check for undefined on browser globals (#462)

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 🌴