freaktechnik/twitch-chatlog

Fetch the chatlog to a twitch VOD from your command line.

twitch-chatlog

Fetch the chatlog to a Twitch VOD from your command line with twitch-chatlog.

This little command can download the whole chat log to a twitch VOD. It takes the ID of the VOD (1111111 or similar) as only argument. To learn about the usage of the command, use twitch-chatlog -h.

The output can optionally be colored with -c or --color or by setting an environment variable TWITCH_CHATLOG_COLOR.

To make use of your own Twitch application client ID, you may provide it as a command line option -C or --client-id or set an environment variable TWITCH_CHATLOG_CLIENT_ID. The default value for client ID is not guaranteed to work past 08 Aug 2016, in which case you will have to supply your own.

To control the part of the chat log to fetch, --start, --length and --end can be used. See the usage section below. By default the command will only fetch the first ten minutes of chat log to minimize the amount of requests.

Installation

npm install -g twitch-chatlog

Usage

Fetch the chat log to a Twitch VOD.
Usage: twitch-chatlog <vod_id>

vod_id is the ID from the VOD URL, optionally prefixed with v (deprecated).

Options:
  -c, --color      Colorize output                    [boolean] [default: false]
  -C, --client-id  Twitch application client ID  [string] [default: (Client-ID)]
  -l, --length     Amount of time from the log to fetch in seconds. Gets
                   shortened to the VOD length if bigger. 0 loads everything but
                   is not recommended. The output will run until the next end of
                   a log fragment.                  [number] [default: (10 min)]
  -s, --start      Start time. Can either be a time relative to the VOD start or
                   actual time.                   [string] [default: "00:00:00"]
  -e, --end        End time. Alternative to specifying a length. A time like for
                   start.                                               [string]
  -r, --raw        Print the raw JSON output instead of a formatted chat log.
                                                      [boolean] [default: false]

  -h, --help       Show help                                           [boolean]
  -v, --version    Show version number                                 [boolean]

Examples:
  twitch-chatlog 79240813                   Load the first ten minutes of chat
                                            for the VOD
                                            https://twitch.tv/ec0ke/v/79040813
  twitch-chatlog -c --end 00:15:00 79240813 Load the first 15 minutes of chat
                                            for the VOD and colorize the output.
  twitch-chatlog 79240813                   Load the chat log until the given
  --end=2016-07-20T20:37:44+0000            date.

Similar Projects

• https://github.com/PetterKraabol/Twitch-Chat-Downloader
• https://github.com/bibby/itch
• https://github.com/OgulcanCelik/twitch-clip-chat

Disclaimer

This program uses an unofficial Twitch API that may stop working at any point. It also potentially sends a lot of requests in quick succession, which might lead to Twitch taking measures against it and thus the program and/or your Twitch experience being reduced.

twitch-chatlog's Issues

SyntaxError: Unexpected token function . why?

im using node v 6.11

using this command got me an SyntaxError: Unexpected token function
im do in it right?

twitch-chatlog 166467795 -C myclientIDxyz

Charity badge

bits-charity: snowflake.

May want a generic badge fallback system.

Allow fetching partial logs

Since fetching logs is pretty request intensive, it should be possible to select time fragments of a log. It should accept two formats: start time + length and start time + end time. The times should either be timestamps of the VOD or absolute times. The selection should most likely be based on the timestamp being smaller than the VOD creation timestamp, if yes assume it is a relative time to the start of the VOD.

If the times are too long (as in, longer than the VOD), there should be an error.

An in-range update of @freaktechnik/eslint-config-test is breaking the build 🚨

The devDependency @freaktechnik/eslint-config-test was updated from 7.0.0 to 7.1.0.

🚨 View failing branch.

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

@freaktechnik/eslint-config-test 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).

---

Commits

The new version differs by 14 commits.

• ca7ffa9 v7.1.0
• e1c66da chore: update some deps here and there
• 74a67c1 feat: add new rules, some of them breaking
• 9aba1d4 add licenses
• a2c45ce Greenkeeper/default/eslint plugin unicorn 16.1.1 (#110)
• a69f1d6 Greenkeeper/default/eslint plugin jsdoc 21.0.0 (#109)
• f46094c Greenkeeper/default/eslint plugin ava 10.2.0 (#108)
• 32dda45 Update eslint-plugin-node in group default to the latest version 🚀 (#105)
• a75f36e Update eslint-import-resolver-webpack in group default to the latest version 🚀 (#104)
• cd7404e Greenkeeper/default/eslint plugin jsdoc 18.0.1 (#102)
• 8c784ac Update eslint-plugin-unicorn in group default to the latest version 🚀 (#101)
• 3846a2b Update eslint-plugin-vue in group default to the latest version 🚀 (#98)
• 961808d Greenkeeper/default/eslint plugin jsdoc 17.0.0 (#97)
• 035e1a4 Update @freaktechnik/eslint-config-base in group meta to the latest version 🚀 (#94)

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

Version 2.1.0 of codecov just got published.

Branch	Build failing 🚨
Dependency	codecov
Current Version	2.0.2
Type	devDependency

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

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

• ✅ dependency-ci Dependencies checked Details

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

Commits

The new version differs by 3 commits .

• f62aab6 Merge pull request #53 from codecov/feature/flags
• d30985e add support for flags
• 3c8fb1b Updating Readme

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 🌴

Support /mes better

Should be ** username instead of <username> and italic when colors are enabled.

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

Version 4.14.1 of express just got published.

Branch	Build failing 🚨
Dependency	express
Current Version	4.14.0
Type	devDependency

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

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

• ✅ dependency-ci Dependencies checked Details

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

Release Notes

4.14.1

• deps: [email protected]
• deps: [email protected]
  • Fix exception when err.headers is not an object
  • deps: statuses@~1.3.1
  • perf: hoist regular expressions
  • perf: remove duplicate validation path
• deps: proxy-addr@~1.1.3
  • deps: [email protected]
• deps: [email protected]
  • deps: http-errors@~1.5.1
  • deps: [email protected]
  • deps: statuses@~1.3.1
• deps: serve-static@~1.11.2
  • deps: [email protected]
• deps: type-is@~1.6.14
  • deps: mime-types@~2.1.13

Commits

The new version differs by 24 commits .

• 0437c51 4.14.1
• 1f70b76 build: [email protected]
• 0b39fa2 build: [email protected]
• 0d6c64f deps: type-is@~1.6.14
• c238aca examples: remove big-view example
• 6b506d8 examples: fix mvc example to ignore files in controllers dir
• dc48f27 deps: update example dependencies
• 8e14e06 deps: serve-static@~1.11.2
• 572657e deps: [email protected]
• cfae537 deps: [email protected]
• a3d6353 deps: proxy-addr@~1.1.3
• a2e323a build: [email protected]
• e73913b build: [email protected]
• ddc93aa deps: [email protected]
• 6723b44 tests: add test for res.sendFile "cacheContol" option

There are 24 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 🌴

Throw a human-readable error when trying to fetch logs of a vod before replay

Rechat was added about a week before the announcement, everything before is log-less.

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

Version 10.2.0 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	10.1.2
Type	devDependency

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

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

• ✅ dependency-ci Dependencies checked Details

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

Commits

The new version differs by 6 commits .

• 455619f chore(release): 10.2.0
• 95cc09a feat: upgrade to version of yargs with extend support (#541)
• 43535f9 chore: explicit update of istanbuljs dependencies (#535)
• 98ebdff feat: allow babel cache to be enabled (#517)
• 50adde4 feat: exclude the coverage/ folder by default 🚀 (#502)
• 6a59834 chore(package): update tap to version 10.0.0 (#507)

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 🌴

content_offset_seconds

Param to the comments API...

getaddrinfo ENOTFOUND rechat.twitch.tv rechat.twitch.tv:443

Hello again. Apologies for the new issue, but since you solved #54 it's now telling me what the actual error is. Not sure what I could be doing wrong, as like I said, it was working fine.

For this test I made sure I updated to the most recent version of twitch-chatlog and node. I also included the Video ID so you can verify that there is chat occurring within the first 60 seconds.

[root@dino ~]# node --version
v7.10.1
[root@dino ~]# twitch-chatlog --version
4.0.1
[root@dino ~]#
[root@dino ~]# twitch-chatlog -p -l 60 -C XXXXXXXXXXXXXXXXXXXX 180455106
{ FetchError: request to https://rechat.twitch.tv/rechat-messages?start=1507399497&video_id=v180455106 failed, reason: getaddrinfo ENOTFOUND rechat.twitch.tv rechat.twitch.tv:443
    at ClientRequest.<anonymous> (/root/.nvm/versions/node/v7.10.1/lib/node_modules/twitch-chatlog/node_modules/node-fetch/lib/index.js:1279:11)
    at emitOne (events.js:96:13)
    at ClientRequest.emit (events.js:191:7)
    at TLSSocket.socketErrorListener (_http_client.js:358:9)
    at emitOne (events.js:96:13)
    at TLSSocket.emit (events.js:191:7)
    at connectErrorNT (net.js:1028:8)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)
  message: 'request to https://rechat.twitch.tv/rechat-messages?start=1507399497&video_id=v180455106 failed, reason: getaddrinfo ENOTFOUND rechat.twitch.tv rechat.twitch.tv:443',
  type: 'system',
  errno: 'ENOTFOUND',
  code: 'ENOTFOUND' }
(node:21807) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): FetchError: request to https://rechat.twitch.tv/rechat-messages?start=1507399497&video_id=v180455106 failed, reason: getaddrinfo ENOTFOUND rechat.twitch.tv rechat.twitch.tv:443
(node:21807) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I see mention on the Twitch dev forums that rechat.twitch.tv isn't officially supported and could change without notice. With that in mind I attempted to dig/ping that domain from multiple machines but it doesn't resolve. Could that be the problem or not really?

Thanks!

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

Version 0.18.1 of ava just got published.

Branch	Build failing 🚨
Dependency	ava
Current Version	0.18.0
Type	devDependency

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

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

• ✅ dependency-ci Dependencies checked Details

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

Release Notes

0.18.1

Quick bug fix: Remove t.is and t.not from enhanced assertion patterns to provide correct output on assertion failure.

Commits

The new version differs by 2 commits .

• dcdfbee 0.18.1
• 154215d remove t.is and t.not from enhanced assertions

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

Version 2.1.0 of eslint-plugin-freaktechnik just got published.

Branch	Build failing 🚨
Dependency	eslint-plugin-freaktechnik
Current Version	2.0.0
Type	devDependency

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

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

• ✅ dependency-ci Dependencies checked Details

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

Commits

The new version differs by 7 commits .

• d1dfb6b 2.1.0
• bc23e80 Update jsdoc
• d1499d6 Allow async as tag anme
• 7df598d fix(package): update eslint-plugin-node to version 4.0.0 (#7)
• 6899ffc docs(readme): add Greenkeeper badge (#6)
• fd154a6 chore(package): update eslint-plugin-ava to version 4.0.0 (#5)
• a8db3b8 chore(package): update eslint-plugin-node to version 3.0.0 (#4)

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 🌴

TypeError: Cannot read property 'status' of undefined

Hello, thanks for this great tool. I had it successfully working just a week ago and was loving it! But without changing anything, it seems to not be working at this time. Do you know if there has been any changes that would be causing the following error:

[root@dino ~]# node --version
v7.6.0
[root@dino ~]#
[root@dino ~]# twitch-chatlog -p -l 60 -C CLIENTID VODID
TypeError: Cannot read property 'status' of undefined
    at searchChat (/root/.nvm/versions/node/v7.6.0/lib/node_modules/twitch-chatlog/lib/index.js:81:22)
    at process._tickCallback (internal/process/next_tick.js:103:7)
(node:17903) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'status' of undefined
(node:17903) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Installed using the following command and got no errors:

npm install -g twitch-chatlog

I've made sure to use node >7.6, and I also tested with 7.10.1 as well.

Also for what it's worth, running --help produces the options/usage without any errors.

Any idea what the problem may be?

An in-range update of @freaktechnik/eslint-config-node is breaking the build 🚨

The devDependency @freaktechnik/eslint-config-node was updated from 6.4.4 to 6.5.0.

🚨 View failing branch.

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

@freaktechnik/eslint-config-node 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).

---

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 sub gifting badge

It's a present, so should be ez

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all 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 we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

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

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

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

• ✅ dependency-ci Dependencies checked Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed 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 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all 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 we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

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

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

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

The devDependency eslint was updated from 5.15.3 to 5.16.0.

🚨 View failing branch.

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

eslint 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.16.0

• dfef227 Build: gensite passes rulesMeta to formatter rendering (#11567) (Kevin Partington)
• c06d38c Fix: Allow HTML formatter to handle no meta data (#11566) (Ilya Volodin)
• 87a5c03 Docs: func-style: clarify when allowArrowFunctions is used (#11548) (Oliver Joseph Ash)
• bc3e427 Update: pass rule meta to formatters RFC 10 (#11551) (Chris Meyer)
• b452f27 Chore: Update README to pull in reviewer data (#11506) (Nicholas C. Zakas)
• afe3d25 Upgrade: Bump js-yaml dependency to fix Denial of Service vulnerability (#11550) (Vernon de Goede)
• 4fe7eb7 Chore: use nyc instead of istanbul (#11532) (Toru Nagashima)
• f16af43 Chore: fix formatters/table test (#11534) (Toru Nagashima)
• 78358a8 Docs: fix duplicate punctuation in CLI docs (#11528) (Teddy Katz)

Commits

The new version differs by 11 commits.

• ded2f94 5.16.0
• ea36e13 Build: changelog update for 5.16.0
• dfef227 Build: gensite passes rulesMeta to formatter rendering (#11567)
• c06d38c Fix: Allow HTML formatter to handle no meta data (#11566)
• 87a5c03 Docs: func-style: clarify when allowArrowFunctions is used (#11548)
• bc3e427 Update: pass rule meta to formatters RFC 10 (#11551)
• b452f27 Chore: Update README to pull in reviewer data (#11506)
• afe3d25 Upgrade: Bump js-yaml dependency to fix Denial of Service vulnerability (#11550)
• 4fe7eb7 Chore: use nyc instead of istanbul (#11532)
• f16af43 Chore: fix formatters/table test (#11534)
• 78358a8 Docs: fix duplicate punctuation in CLI docs (#11528)

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 🌴

Try to guess VOD ID if there is an absolute start or end time with additional channel param

Use the minimum VOD age to detect that. So the command either requires a VOD ID or an absolute time plus a channel.

An in-range update of @freaktechnik/eslint-config-node is breaking the build 🚨

The devDependency @freaktechnik/eslint-config-node was updated from 7.0.0 to 7.1.0.

🚨 View failing branch.

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

@freaktechnik/eslint-config-node 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).

---

Commits

The new version differs by 14 commits.

• ca7ffa9 v7.1.0
• e1c66da chore: update some deps here and there
• 74a67c1 feat: add new rules, some of them breaking
• 9aba1d4 add licenses
• a2c45ce Greenkeeper/default/eslint plugin unicorn 16.1.1 (#110)
• a69f1d6 Greenkeeper/default/eslint plugin jsdoc 21.0.0 (#109)
• f46094c Greenkeeper/default/eslint plugin ava 10.2.0 (#108)
• 32dda45 Update eslint-plugin-node in group default to the latest version 🚀 (#105)
• a75f36e Update eslint-import-resolver-webpack in group default to the latest version 🚀 (#104)
• cd7404e Greenkeeper/default/eslint plugin jsdoc 18.0.1 (#102)
• 8c784ac Update eslint-plugin-unicorn in group default to the latest version 🚀 (#101)
• 3846a2b Update eslint-plugin-vue in group default to the latest version 🚀 (#98)
• 961808d Greenkeeper/default/eslint plugin jsdoc 17.0.0 (#97)
• 035e1a4 Update @freaktechnik/eslint-config-base in group meta to the latest version 🚀 (#94)

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 🌴

Switch to API v5

https://blog.twitch.tv/action-required-twitch-api-version-update-f3a21e6c3410#.yqgbmc9cz

Probably not much to change other than a header or two and maybe a sliver of how things work.

Refactor all the formatting to use streams

For best reliability, not just the JSON formatting but also the formatted text output should be stream based. Would also allow output as it's loaded, at least for the formatted text case, and as such replace the progress option. Definitely a major release.
Labeling as enhancement, even if it is in some cases a bug.

Add partner checkmark badge

Should be the same purple as turbo afaik.

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

Version 7.1.0 of yargs just got published.

Branch	Build failing 🚨
Dependency	yargs
Current Version	7.0.2
Type	dependency

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

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

• ✅ dependency-ci Dependencies checked Details

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

Commits

The new version differs by 8 commits .

• e7359d6 chore(release): 7.1.0
• c357412 docs: switch to conventional commits badge [ci skip] (#850)
• 17e89bd fix: we shouldn't output help if we've printed a prior help-like message (#847)
• 50c9acd chore: add editorconfig (#848)
• 360e301 fix: get terminalWidth in non interactive mode no longer causes a validation exception (#837)
• fde0564 feat: add support for numeric commands (#825)
• c748dd2 fix: fix demandOption no longer treats 'false' as truthy (#829)
• e0b4efb test: Made unit test passing with node-chakracore

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 🌴

Clip Champ Badge

Syntax Error: Unexpected Token =

The error is found in the index file on line 63:
function searchChat(start, length, vodID, c = false, progress = false, workerCount = 1, testServer) {...

I installed node version 4.6.0, NPM version 2.15.9
I then followed instructions and installed via 'npm install -g twitch-chatlog'

In the nodejs directory I ran 'twitch-chatlog v94562809' and the error popped. I went through all of the examples and they popped the same error as well.

I am new to node.js, so any help would be appreciated!

Best,

Aspen

JSON.stringify() range error - invalid string length

When attempting to fetch a chatlog for a VOD with over ~600k-700k+ chats, e.g. a 24 hour XQC VOD (888381698), the following error is thrown.

RangeError: Invalid string length
    at JSON.stringify (<anonymous>)
    at C:\....\node_modules\twitch-chatlog\bin\twitch-chatlog:90:21

This appears to be the max string size or max possible string size that can be "stringified"

Split tests for chat-stream out of get-chatlog tests

Heads up: API Client ID has expired

Just letting you know that the client ID that's baked in has now expired. Substituting a valid ID with -C works just fine, though. Maybe worth updating the README and removing the default ID. Maybe fail with a warning if no ID is given on the commandline?

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

The dependency yargs was updated from 13.2.2 to 13.2.4.

🚨 View failing branch.

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

yargs 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).

---

Commits

The new version differs by 14 commits.

• a6e67f1 chore(release): 13.2.4
• fc13476 chore: update standard-verison dependency
• bf46813 fix(i18n): rename unclear 'implication failed' to 'missing dependent arguments' (#1317)
• a3a5d05 docs: fix a broken link to MS Terminology Search (#1341)
• b4f8018 build: add .versionrc that hides test/build
• 0c39183 chore(release): 13.2.3
• 08e0746 chore: update deps (#1340)
• 843e939 docs: make --no- boolean prefix easier to find in the docs (#1338)
• 84cac07 docs: restore removed changelog of v13.2.0 (#1337)
• b20db65 fix(deps): upgrade cliui for compatibility with latest chalk. (#1330)
• c294d1b test: accept differently formatted output (#1327)
• ac3f10c chore: move .hbs templates into .js to facilitate webpacking (#1320)
• 0295132 fix: address issues with dutch translation (#1316)
• 9f2468e doc: clarify parserConfiguration object structure (#1309)

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

Version 1.7.0 of node-fetch just got published.

Branch	Build failing 🚨
Dependency	node-fetch
Current Version	1.6.3
Type	dependency

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

node-fetch 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

• ✅ dependency-ci Dependencies checked Details
• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

v1.7.0

This is a backport maintenance release, see changelog for details

Commits

The new version differs by 8 commits.

• cf71a1b 1.7.0
• 0f09608 try to fix travis build config again
• 93d5eb6 update travis to only install old npm for older node release
• 8e11298 pin npm at an older version for node 0.10 support
• f43c6a6 update readme badge
• 2fca3e9 switch 1.x branch to codecov as well
• 3043012 revert error handling for no-content json response
• 325f13d commit to allow some feature backport in 1.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 🌴

Properly handle no rechat

Rechat returns a 404 when there are no fragments for a video. Can actually just print the rechat error there.

This means that a pilot fragment should be fetched first and then decide to fetch more or not.

Support bits-leader badge

Version is the rank

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

The devDependency codecov was updated from 3.6.4 to 3.6.5.

🚨 View failing branch.

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

codecov 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 2 commits.

• ebe132e 3.6.5
• 02cf13d [CE-1330] Escaping args (#167)

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 🌴

Cheer badges

An in-range update of @freaktechnik/eslint-config-test is breaking the build 🚨

The devDependency @freaktechnik/eslint-config-test was updated from 6.4.4 to 6.5.0.

🚨 View failing branch.

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

@freaktechnik/eslint-config-test 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).

---

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 🌴

Map basic cheer emotes to the ascii characters

The basic cheer emotes (bitsX) should map to the same characters and colors as are used for the badges.

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

Version 3.14.1 of eslint just got published.

Branch	Build failing 🚨
Dependency	eslint
Current Version	3.14.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

• ✅ dependency-ci Dependencies checked Details

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

Release Notes

v3.14.1

• 791f32b Fix: brace-style false positive for keyword method names (fixes #7974) (#7980) (Teddy Katz)
• d7a0add Docs: Add ESLint tutorial embed to getting started (#7971) (Jamis Charles)
• 72d41f0 Fix: no-var autofix syntax error in single-line statements (fixes #7961) (#7962) (Teddy Katz)
• b9e5b68 Fix: indent rule crash on sparse array with object (fixes #7959) (#7960) (Gyandeep Singh)
• a7bd66a Chore: Adding assign/redeclare tests to no-undefined (refs #7964) (#7965) (Kevin Partington)
• 8bcbf5d Docs: typo in prefer-promise-reject-errors (#7958) (Patrick McElhaney)

Commits

The new version differs by 8 commits .

• e544644 3.14.1
• 1297635 Build: package.json and changelog update for 3.14.1
• 791f32b Fix: brace-style false positive for keyword method names (fixes #7974) (#7980)
• d7a0add Docs: Add ESLint tutorial embed to getting started (#7971)
• 72d41f0 Fix: no-var autofix syntax error in single-line statements (fixes #7961) (#7962)
• b9e5b68 Fix: indent rule crash on sparse array with object (fixes #7959) (#7960)
• a7bd66a Chore: Adding assign/redeclare tests to no-undefined (refs #7964) (#7965)
• 8bcbf5d Docs: typo in prefer-promise-reject-errors (#7958)

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 🌴

Add loading progress bar

This should be pretty straight forward. Each promise that is resolved increases the progress. It should be disableable with an argument.

connect ETIMEDOUT 31.13.85.1:443

I use npm i install twitch-chatlog in my windowspower shell but it can't link to some address.
I tried proxy but it still didn't work.

Here is the error.

PS D:\lydia\life\candycrash> twitch-chatlog 79240813
{ FetchError: request to https://api.twitch.tv/kraken/videos/79240813 failed, reason: connect ETIMEDOUT 31.13.85.1:443
at ClientRequest. (C:\Users\TF\AppData\Roaming\npm\node_modules\twitch-chatlog\node_modules\node-fetch\lib\index.js:1455:11)
at emitOne (events.js:116:13)
at ClientRequest.emit (events.js:211:7)
at TLSSocket.socketErrorListener (_http_client.js:387:9)
at emitOne (events.js:116:13)
at TLSSocket.emit (events.js:211:7)
at emitErrorNT (internal/streams/destroy.js:64:8)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
message: 'request to https://api.twitch.tv/kraken/videos/79240813 failed, reason: connect ETIMEDOUT 31.13.85.1:443',
type: 'system',
errno: 'ETIMEDOUT',
code: 'ETIMEDOUT' }
(node:11168) UnhandledPromiseRejectionWarning: FetchError: request to https://api.twitch.tv/kraken/videos/79240813 failed, reason: connect ETIMEDOUT 31.13.85.1:443
at ClientRequest. (C:\Users\TF\AppData\Roaming\npm\node_modules\twitch-chatlog\node_modules\node-fetch\lib\index.js:1455:11)
at emitOne (events.js:116:13)
at ClientRequest.emit (events.js:211:7)
at TLSSocket.socketErrorListener (_http_client.js:387:9)
at emitOne (events.js:116:13)
at TLSSocket.emit (events.js:211:7)
at emitErrorNT (internal/streams/destroy.js:64:8)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
(node:11168) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:11168) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Support Clips

Support fetching the chatlog from clips. This probably involves getting the VOD ID for the clip and the start offset. Or maybe there's a dedicated chat replay API.

Don't allow removal of channel as correction

At least for multichannel bots.

Better badges

Staff is wrench on black bg
Axe is global mod
Shield is admin?