xuset/aether-torrent

A single WebTorrent client shared by all web pages and workers

aether-torrent's Issues

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

Version 16.2.2 of browserify was just published.

Branch	Build failing 🚨
Dependency	browserify
Current Version	16.2.1
Type	devDependency

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

browserify 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

v16.2.2

Remove some extraneous files from the published package.

Commits

The new version differs by 1 commits.

• fc30e50 16.2.2

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 🌴

THANK YOU

Vanilla WebTorrent was giving us a hard time. This project is super straight forward to use. Thank you.

An in-range update of simple-get is breaking the build 🚨

Version 3.0.3 of simple-get was just published.

Branch	Build failing 🚨
Dependency	simple-get
Current Version	3.0.2
Type	dependency

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

simple-get 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 failed (Details).

---

Commits

The new version differs by 6 commits.

• 7173ab4 3.0.3
• bda9500 Support { form: {}, json: true } use case
• f5a38d4 Merge pull request #40 from feross/add-gitignore-update-travis
• f72f88d restricted .gitignore to more relevant things
• 813fd13 Make supported node version explicit in travis
• 22a5f69 Added .gitignore

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 🌴

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

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

Version 0.98.24 of webtorrent was just published.

Branch	Build failing 🚨
Dependency	webtorrent
Current Version	0.98.23
Type	dependency

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

webtorrent 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 failed Details

---

Commits

The new version differs by 23 commits.

• b9f3777 build
• 7cb8f71 authors
• 9a4a657 0.98.24
• e7d6e4f Merge pull request #1260 from diracdeltas/fix/add-hostname-opt
• 7c107e6 simplify double if statement
• fb20cfd Merge pull request #1320 from webtorrent/airtap-test
• eb3ea14 Remove bin/test.js
• 18cf763 Merge pull request #1319 from webtorrent/greenkeeper/airtap-0.0.4
• d7edb30 chore(package): update airtap to version 0.0.4
• fad0ca6 Merge pull request #1315 from webtorrent/greenkeeper/airtap-0.0.3
• beb00a0 chore(package): update airtap to version 0.0.3
• c6a8092 Merge pull request #1311 from webtorrent/greenkeeper/airtap-0.0.2
• 1685fdc chore(package): update airtap to version 0.0.2
• 24d3af0 Merge pull request #1308 from webtorrent/greenkeeper/simple-peer-9.0.0
• 2a998b7 Merge pull request #1309 from webtorrent/airtap

There are 23 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 standard is breaking the build 🚨

Version 10.0.3 of standard just got published.

Branch	Build failing 🚨
Dependency	standard
Current Version	10.0.2
Type	devDependency

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

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

v10.0.3

• Internal changes (incremented dependency versions)

Commits

The new version differs by 99 commits.

• 91e80a1 10.0.3
• 82a0d5c changelog
• d22676e Merge pull request #963 from daper/patch-1
• cfb84fe Remove tilde to lock down eslint-config-standard-jsx version
• 4a6e0d0 Update dependecy of eslint-config-standard-jsx
• ac9e09e Merge pull request #961 from igorsantos07/patch-1
• 873bc9b Adding valid example for no-unsafe-negation
• f00b169 more feross/standard -> standard/standard
• 9770303 Merge pull request #954 from standard/security
• 8cc2285 Add a security policy
• 2fa8b0f change more feross/standard -> standard/standard
• e79a692 Merge branch 'devjin0617-translation-kr'
• 34490f7 Merge branch 'translation-kr' of https://github.com/devjin0617/standard into devjin0617-translation-kr
• 6d59566 Merge pull request #953 from standard/translations
• 3895bc6 move english readme/rules to docs/ folder

There are 99 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 karma-chrome-launcher is breaking the build 🚨

Version 2.2.0 of karma-chrome-launcher just got published.

Branch	Build failing 🚨
Dependency	karma-chrome-launcher
Current Version	2.1.1
Type	devDependency

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

As karma-chrome-launcher 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

v2.2.0

Features

• add ChromiumHeadless (7a12021)

Commits

The new version differs by 6 commits.

• b01cea1 chore: release v2.2.0
• 40e96e2 chore: update contributors
• 998824d Merge pull request #135 from ishitatsuyuki/chromium-headless
• 7a12021 feat: add ChromiumHeadless
• 96d84aa Merge pull request #126 from mgol/patch-1
• 2a02494 refactor: remove incorrect comment

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

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

Version 5.9.0 of parse-torrent was just published.

Branch	Build failing 🚨
Dependency	parse-torrent
Current Version	5.8.3
Type	dependency

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

parse-torrent 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 failed Details

---

Commits

The new version differs by 10 commits.

• a0bd6ea 5.9.0
• e7d38d4 Merge parse-torrent-file into this package
• 429611b zuul -> airtap
• 80f1d3f zuul: drop ie, flaky android, add iphone
• 5fedae8 Merge pull request #57 from webtorrent/greenkeeper/get-stdin-6.0.0
• 73af9b2 fix(package): update get-stdin to version 6.0.0
• 2c9a254 remove greenkeeper badge
• a3362d1 Merge pull request #50 from webtorrent/greenkeeper/initial
• fc25fef Update README.md
• 10c31e7 docs(readme): add Greenkeeper badge

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

Version 3.0.4 of uglify-js just got published.

Branch	Build failing 🚨
Dependency	uglify-js
Current Version	3.0.3
Type	devDependency

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

As uglify-js 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.0.4

 

Commits

The new version differs by 5 commits0.

• daaefc1 v3.0.4
• 1d407e7 fix invalid transform on const (#1919)
• 2b44f4a update README (#1918)
• e51c354 fix typo (#1913)
• 3bf1946 update documentation (#1909)

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

The devDependency watchify was updated from 3.11.0 to 3.11.1.

🚨 View failing branch.

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

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

• c3fe218 3.11.1
• e90101b Merge pull request #362 from digipost/upgrade-deps
• d163b4f upgrade dependencies: fix errors from npm audit
• 1917270 Merge pull request #351 from menzow/feature/update-docs
• d232754 Merge pull request #357 from Kamil93/patch-1
• d924e9b Update readme.markdown
• 9ea8a65 Support for working with transforms
• 8147bc5 Add troubleshooting information for silenced errors

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

Version 3.2.1 of uglify-js was just published.

Branch	Build failing 🚨
Dependency	uglify-js
Current Version	3.2.0
Type	devDependency

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

uglify-js 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

v3.2.1

 

Commits

The new version differs by 17 commits.

• b9f3ddf v3.2.1
• 77332a0 fix dead_code on for (#2552)
• 85c56ad more tests for #2535 (#2551)
• 8da3754 improve evaluate on typeof (#2550)
• 9a6b11f improve boolean compression (#2548)
• 7ac6fdc improve switch case compression (#2547)
• f6610ba improve AST_For.init & AST_Switch.expression compression (#2546)
• 09b320e convert to number under boolean context (#2545)
• 5a1e99d improve compression of if conditions (#2544)
• b762f2d improve compression of loop conditions (#2543)
• 172079a improve code reuse (#2542)
• c58d393 fix corner case in call binding (#2541)
• 18302bf backport test from #2526 (#2534)
• bc5047c fix inline on nested substitutions (#2533)
• 206a54a fix nested hoist_props substitution (#2523)

There are 17 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 mime is breaking the build 🚨

The dependency mime was updated from 2.3.1 to 2.4.0.

🚨 View failing branch.

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

mime 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 failed (Details).

---

Commits

The new version differs by 7 commits.

• a246724 chore(release): 2.4.0
• 40f3995 chore: security updates
• 49e6e41 feat: update to [email protected]
• b9a1431 update mocha (fixes growl security issue)
• c013a08 Merge pull request #190 from marijnh/master
• 9d2a7b8 feat: Bind exported methods
• abcb6e1 chore: travis tests badge

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

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

Version 2.12.0 of render-media was just published.

Branch	Build failing 🚨
Dependency	render-media
Current Version	2.11.0
Type	dependency

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

render-media 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 failed Details

---

Commits

The new version differs by 9 commits.

• 641c62b 2.12.0
• 71112a0 Add FLAC support
• e74f507 Merge pull request #35 from feross/greenkeeper/initial
• fa853d2 remove greenkeeper badge
• 25e3e75 Merge pull request #36 from feross/revert-34-patch-1
• 49fe70c zuul: drop ie + flaky android, add iphone
• 91dcdb1 Revert "Fix chrome issue with opus webm videos"
• 1508c2c docs(readme): add Greenkeeper badge
• 8a1f03b chore(package): update dependencies

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 🌴