Coder Social home page Coder Social logo

livestreamer-twitch-followed's People

Contributors

alexdubois-collibra avatar greenkeeper[bot] avatar skiant avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar

livestreamer-twitch-followed's Issues

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

Version 11.3.0 of eslint-config-airbnb-base just got published.

Branch Build failing 🚨
Dependency eslint-config-airbnb-base
Current Version 11.2.0
Type devDependency

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

As eslint-config-airbnb-base 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

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

Version 6.26.0 of babel-cli just got published.

Branch Build failing 🚨
Dependency babel-cli
Current Version 6.24.1
Type devDependency

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

As babel-cli 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

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

The dependency request-promise-native was updated from 1.0.5 to 1.0.6.

🚨 View failing branch.

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

request-promise-native 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.

  • 7ad655a Version 1.0.6 (now really)
  • 1240b80 fix: updated indirect lodash dependency to fix security vulnerability
  • 80947a1 Version 1.0.6
  • ad529a3 chore: fix ci build for node v8+
  • c2c54c4 Merge pull request #33 from jasonmit/u/jasonmit/fix-node-6
  • 67f7ed2 Merge branch 'master' into u/jasonmit/fix-node-6
  • 4633d4c fix: breaking change in tough-cookie v3
  • 14aa6ee chore: added node 8 and 10 to ci build
  • 9cfcaaa Update package.json
  • 049152b fix: target tough-cookie 2.x to preserve node 6 support

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

The dependency chalk was updated from 2.4.1 to 2.4.2.

🚨 View failing branch.

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

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

Release Notes for v2.4.2

This release is done from the v2-release branch, as master branch targets the work-in-progress v3 release.

Commits

The new version differs by 2 commits.

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 @types/request-promise-native is breaking the build 🚨

The devDependency @types/request-promise-native was updated from 1.0.15 to 1.0.16.

🚨 View failing branch.

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

@types/request-promise-native 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).

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 @oclif/test is breaking the build 🚨

The devDependency @oclif/test was updated from 1.2.2 to 1.2.4.

🚨 View failing branch.

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

@oclif/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).

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

Version 3.5.2 of bluebird was just published.

Branch Build failing 🚨
Dependency bluebird
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.

bluebird 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 v3.5.2

Bugfixes:

  • Fix PromiseRejectionEvent to contain .reason and .promise properties. (#1509, #1464)
  • Fix promise chain retaining memory until the entire chain is resolved (#1544, #1529)

id: changelog
title: Changelog

Commits

The new version differs by 22 commits.

  • 50067ec Release v3.5.2
  • f290da0 Fix memory being retained until promise queue is completely empty (#1544)
  • ad6d763 Update benchmarks (#1539)
  • 49da1ac Fix a typo. (#1534)
  • b06106a Fix typo in readme introduced in #1530 (#1531)
  • c1dc5b9 Update README.md (#1530)
  • e35455f chore: clone last 5 commits (#1521)
  • 91ae9ce chore: add Node.js 10 (#1523)
  • 9159472 Added a simple usage example (#1369)
  • 39081ba Update promise.each.md (#1479)
  • 77781fe Fix header (#1513)
  • b8eedc1 Update LICENSE to 2018 (#1490)
  • 4163e82 Added ES6 way to import the bluebird promise (#1461)
  • 3790a92 DOC: add direct link to Promise.delay from API ref (#1465)
  • e8d8525 Update error documentation (#1469)

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

The dependency request was updated from 2.88.0 to 2.88.2.

🚨 View failing branch.

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

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

The devDependency nyc was updated from 13.1.0 to 13.2.0.

🚨 View failing branch.

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

nyc 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 17 commits.

  • 29e6f5e chore(release): 13.2.0
  • e95856c chore: Update dependencies. (#978)
  • 921d386 fix: Create directory for merge destination. (#979)
  • df2730d feat: Option Plugins (#948)
  • 35cd49a feat: document the fact that cacheDir is configurable (#968)
  • ff834aa feat: avoid hardcoded HOME for spawn-wrap working dir (#957)
  • 35710b1 build: move windows tests to travis (#961)
  • 93cb5c1 tests: coverage for temp-dir changes (#964)
  • d566efe test: stop using LAZY_LOAD_COUNT (#960)
  • f23d474 chore: update stale bot config with feedback (#958)
  • 62d7fb8 chore: slight tweak to position of test
  • 28b6d09 fix: missing command temp-directory (#928)
  • 40afc5f fix: nyc processing files not covered by include when all is enabled. (#914)
  • ba22a26 docs(readme): Update to reflect .nycrc.json support (#934)
  • 2dbb82d chore: enable probot-stale

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 @oclif/config is breaking the build 🚨

The dependency @oclif/config was updated from 1.8.8 to 1.9.0.

🚨 View failing branch.

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

@oclif/config 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).

Release Notes for v1.9.0

1.9.0 (2018-11-07)

Features

Commits

The new version differs by 2 commits.

  • 3086696 chore(release): 1.9.0 [skip ci]
  • 5778618 feat: use esModuleInterop when defined (fixes #179) (#61)

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 @types/chai is breaking the build 🚨

The devDependency @types/chai was updated from 4.1.7 to 4.2.0.

🚨 View failing branch.

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

@types/chai 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).

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

Version 3.1.0 of inquirer just got published.

Branch Build failing 🚨
Dependency inquirer
Current Version 3.0.6
Type dependency

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

inquirer 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
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes v3.1.0
  • password prompt can now rendered hidden input (Unix style)
  • filter function now also receive the current answers as argument
  • Smaller package size
Commits

The new version differs by 17 commits.

  • e612cc5 3.1.0
  • 148cb71 Update eslint-config-xo-space to the latest version πŸš€ (#516)
  • 3b93dd5 call chalk.reset() after message prompt (#544)
  • 3ff39a6 chore(package): update chai to version 4.0.1 (#541)
  • 76f1bfe upgrade external-editor to 2.0.4 (#535)
  • da4eceb pass current answers hash to filter (#533)
  • f99b398 Use rx-lite-aggregates instead of full rx (#532)
  • 20119a2 fix(package): update ansi-escapes to version 2.0.0 (#527)
  • e294e16 Update validate fn param docs (#526)
  • 5b3a4a2 Add masked password example
  • 9de81a8 Fix linting of tests
  • d7db156 Add some tests
  • 50a9beb Switch conditionals
  • 379e0aa Inform user that input is hidden
  • bf28e76 Password prompt should display no characters

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

Version 2.5.0 of eslint-plugin-import just got published.

Branch Build failing 🚨
Dependency eslint-plugin-import
Current Version 2.3.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-import 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 27 commits.

  • c41ed06 bump to v2.5.0
  • 94187a3 bump debug version everywhere
  • 54687d1 resolvers/webpack: v0.8.2
  • dac23a1 eslint-module-utils: v2.1.1 (bumping to re-publish to npm)
  • d92ef43 Merge pull request #696 from eelyafi/new_line_fixer
  • 3f9e4bf [Tests] comment out failing (and probably invalid) test
  • 4067495 Only apps should have lockfiles.
  • ebaa8e3 Merge pull request #873 from lukeapage/patch-3
  • 3268cb1 Fix documentation of newline-after-import example
  • 3c46d30 rollback utils dependency to 2.0.0
  • e3a32ad add yank note to utils change log
  • 089f7f1 add yanking note to root change log
  • dfbe0e7 Upgrade debug version of eslint-module-utils (#844)
  • 3d9c642 Merge branch 'release'
  • b8e9a0b Merge pull request #861 from benmosher/release-2.4.0

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

Version 7.1.0 of babel-loader just got published.

Branch Build failing 🚨
Dependency babel-loader
Current Version 7.0.0
Type devDependency

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

As babel-loader 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 7.1.0

πŸš€ New Feature

  • Update to support webpack 3 (#471) (Joe Lencioni)
  • look for babel options in package.json and .babelrc.js (babel 7) (#465) (Thomas Sileghem)
  • Watch configuration files. (#460) (Evilebot Tnawi)
    You can now change the babel config while webpack watch or dev-server is running and webpack will correctly recompile all files with babel.

πŸ› Bug Fix

  • Only base cache identifier on babel options from package.json (#468) (Daniel Tschinder)

πŸ“ Documentation

  • Remove outdated examples. (Daniel Tschinder)

🏠 Internal

  • update eslint-config-babel to version 7.0.0 (#469) (greenkeeper[bot])
  • update lint-staged to version 4.0.0 (#470) (greenkeeper[bot])
  • Add prettier eslint plugin (#466) (Daniel Tschinder)
  • Add node 8 to test matrix (#467) (Daniel Tschinder)
  • Upgrade find-cache-dir to 1.0 and cross-env to 5.0 (#457) (Daniel Tschinder)
Commits

The new version differs by 13 commits.

  • d249119 7.1.0
  • ea9b4d4 Update yarn.lock
  • 7986787 chore(package): update eslint-config-babel to version 7.0.0 (#469)
  • ee40748 chore(package): update lint-staged to version 4.0.0 (#470)
  • 66784e4 Update to webpack 3 (#471)
  • 8544ffa Only base cache identifier on babel options from pkg.json (#468)
  • ea2eafa Add prettier eslint plugin (#466)
  • 4548169 Add node 8 to test matrix (#467)
  • d8b73c0 fix(resolve-rc): look for babel in package.json and .babelrc.js (#465)
  • 8d96c1f Remove outdated examples.
  • 91f2658 Fixed: watch configuration files. (#460)
  • de2d3f3 Upgrade dependencies
  • 37e63e3 Upgrade find-cache-dir to 1.0 and cross-env to 5.0 (#457)

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 @types/mocha is breaking the build 🚨

The devDependency @types/mocha was updated from 5.2.5 to 5.2.6.

🚨 View failing branch.

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

@types/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).

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 @oclif/command is breaking the build 🚨

The dependency @oclif/command was updated from 1.5.4 to 1.5.5.

🚨 View failing branch.

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

@oclif/command 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).

Release Notes for v1.5.5

1.5.5 (2018-11-12)

Bug Fixes

  • construct full help message for known Command (#50) (5ef4e3c)
Commits

The new version differs by 3 commits.

  • 34ce45b chore(release): 1.5.5 [skip ci]
  • b94b5f5 chore: updated deps
  • 5ef4e3c fix: construct full help message for known Command (#50)

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 @oclif/plugin-help is breaking the build 🚨

The dependency @oclif/plugin-help was updated from 2.1.3 to 2.1.4.

🚨 View failing branch.

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

@oclif/plugin-help 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).

Release Notes for v2.1.4

2.1.4 (2018-11-12)

Bug Fixes

Commits

The new version differs by 3 commits.

  • 0777d50 chore(release): 2.1.4 [skip ci]
  • a7fe1c1 chore: updated deps
  • 0c0a0d9 fix: Expose command help method (#33)

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

Version 3.3.0 of babel-plugin-lodash was just published.

Branch Build failing 🚨
Dependency babel-plugin-lodash
Current Version 3.2.11
Type devDependency

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

babel-plugin-lodash 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 🌴

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from 10.12.0 to 10.12.1.

🚨 View failing branch.

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

@types/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).

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

Version 1.8.0 of eslint-loader just got published.

Branch Build failing 🚨
Dependency eslint-loader
Current Version 1.7.1
Type devDependency

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

As eslint-loader 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 1.8.0
Commits

The new version differs by 10 commits.

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

The dependency tslib was updated from 1.9.3 to 1.10.0.

🚨 View failing branch.

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

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

Release Notes for tslib 1.10.0

This release fixes enumerability in object rest's __rest helper (see details here) and adds a new __spreadArrays helper (done as part of a change for more accurate array spreads).

Commits

The new version differs by 5 commits.

  • e1aae12 Update version to '1.10.0'.
  • ab40523 Add '__spreadArrays' helper (#67)
  • 57efce4 Modified __rest to check if property is enumerable. (#66)
  • ca03390 Merge pull request #57 from styfle/patch-1
  • b99cbbc Update .npmignore

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

Version 6.4.1 of babel-loader just got published.

Branch Build failing 🚨
Dependency babel-loader
Current Version 6.4.0
Type devDependency

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

As babel-loader 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 v6.4.1

πŸ› Bug Fix

Commits

The new version differs by 2 commits .

  • 48325ea 6.4.1
  • f3241f8 Fixed reset of BABEL_ENV when options.forceEnv is used (#420)

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

Version 4.17.5 of lodash was just published.

Branch Build failing 🚨
Dependency lodash
Current Version 4.17.4
Type dependency

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

lodash 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

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

The devDependency ts-node was updated from 8.0.3 to 8.1.0.

🚨 View failing branch.

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

ts-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 4 commits.

  • d117650 8.1.0
  • 66d54af Cache file system operations (#803)
  • 038f83d Remove incremental & tsBuildInfoFile compiler opts (#815)
  • 750ecca Add --log-error option (#818)

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 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.