Code Monkey home page Code Monkey logo

boxen-notify.js's People

Contributors

dependabot[bot] avatar greenkeeper[bot] avatar greenkeeperio-bot avatar jokeyrhyme avatar

Stargazers

 avatar

Watchers

 avatar  avatar

boxen-notify.js's Issues

An in-range update of boxen is breaking the build ๐Ÿšจ

Version 1.2.1 of boxen just got published.

Branch Build failing ๐Ÿšจ
Dependency boxen
Current Version 1.2.0
Type dependency

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

boxen 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/appveyor/branch Waiting for AppVeyor build to complete 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.

  • f8bcc51 1.2.1
  • 4f1bf89 Add support for margin right with float right (#22)

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
  • The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

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 eslint-plugin-import is breaking the build ๐Ÿšจ

The devDependency eslint-plugin-import was updated from 2.16.0 to 2.17.0.

๐Ÿšจ View failing branch.

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

eslint-plugin-import 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/appveyor/branch: Waiting for AppVeyor build to complete (Details).
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 61 commits.

  • 0499050 bump to v2.17.0
  • f479635 [webpack] v0.11.1
  • 8a4226d Merge pull request #1320 from bradzacher/export-ts-namespaces
  • 988e12b fix(export): Support typescript namespaces
  • 70c3679 [docs] make rule names consistent
  • 6ab25ea [Tests] skip a TS test in eslint < 4
  • 405900e [Tests] fix tests from #1319
  • 2098797 [fix] export: false positives for typescript type + value export
  • 70a59fe [fix] Fix overwriting of dynamic import() CallExpression
  • e4850df [ExportMap] fix condition for checking if block comment
  • 918567d [fix] namespace: add check for null ExportMap
  • 2d21c4c Merge pull request #1297 from echenley/ech/fix-isBuiltIn-local-aliases
  • 0ff1c83 [dev deps] lock typescript to ~, since it doesnโ€™t follow semver
  • 40bf40a [*] [deps] update resolve
  • 28dd614 Merge pull request #1304 from bradennapier/feature/typescript-export-type

There are 61 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 eslint-plugin-import is breaking the build ๐Ÿšจ

The devDependency eslint-plugin-import was updated from 2.17.3 to 2.18.0.

๐Ÿšจ View failing branch.

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

eslint-plugin-import 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/appveyor/branch: Waiting for AppVeyor build to complete (Details).
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 26 commits.

  • c924f5d Bump to v2.18.0
  • c8132f2 Merge pull request #1393 from sheepsteak/eslint-6
  • 7e41d29 Make testVersion take a function to delay running require.resolve
  • d7023f6 Remove ESLint 6 from allowed failures in Travis
  • 3bee716 Use eslint@6 instead of [email protected] in Travis
  • d9b7258 Only run tests using typescript-eslint-parser on eslint@<6
  • c2b19d0 Update to @typescript-eslint/parser canary
  • 2f1f4da Allow ESLint@6
  • e6ea127 Use require.resolve when passing parser to RuleTester
  • 1029b4f Add ecmaVersion when required
  • b5ff64e Transform output of FileEnumerator into what rule expects
  • fc65509 Merge pull request #1389 from fooloomanzoo/patch-1
  • 4140870 Update no-named-as-default-member.md
  • 58b41c2 Merge pull request #1383 from golopot/node-12
  • 8974346 [Build] make node 12 pass CI

There are 26 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 eslint-plugin-import is breaking the build ๐Ÿšจ

Version 2.4.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
  • โŒ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 10 commits.

  • 44ca158 update utils changelog
  • a3728d7 bump eslint-module-utils to v2.1.0
  • 3e29169 bump v2.4.0
  • ea9c92c Merge pull request #737 from kevin940726/master
  • 8f9b403 fix typos, enforce type of array of strings in allow option
  • 95315e0 update CHANGELOG.md
  • 28e1623 eslint-module-utils: filePath in parserOptions (#840)
  • 2f690b4 update CI to build on Node 6+7 (#846)
  • 7d41745 write doc, add two more tests
  • dedfb11 add allow glob for rule no-unassigned-import, fix #671

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.6.1 of eslint just got published.

Branch Build failing ๐Ÿšจ
Dependency eslint
Current Version 4.6.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/appveyor/branch Waiting for AppVeyor build to complete Details
  • โŒ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v4.6.1
  • bdec46d Build: avoid process leak when generating website (#9217) (Teddy Katz)
  • cb74b87 Fix: avoid adding globals when an env is used with false (fixes #9202) (#9203) (Teddy Katz)
  • f9b7544 Docs: Correct a typo in generator-star-spacing documentation (#9205) (Ethan Rutherford)
  • e5c5e83 Build: Fixing issue with docs generation (Fixes #9199) (#9200) (Ilya Volodin)
Commits

The new version differs by 6 commits.

  • d65c540 4.6.1
  • 61c845c Build: changelog update for 4.6.1
  • bdec46d Build: avoid process leak when generating website (#9217)
  • cb74b87 Fix: avoid adding globals when an env is used with false (fixes #9202) (#9203)
  • f9b7544 Docs: Correct a typo in generator-star-spacing documentation (#9205)
  • e5c5e83 Build: Fixing issue with docs generation (Fixes #9199) (#9200)

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 ๐Ÿšจ

The devDependency eslint-plugin-import was updated from 2.17.1 to 2.17.2.

๐Ÿšจ View failing branch.

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

eslint-plugin-import 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/appveyor/branch: Waiting for AppVeyor build to complete (Details).
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 5 commits.

  • eddcfa9 Bump to v2.17.2
  • b151d04 [fix] no-unused-modules: avoid crash when using ignoreExports-option
  • 3512563 [fix] no-unused-modules: make sure that rule with no options will not fail
  • 8e0c021 [Test] no-unused-modules add failing test case
  • 9b7a970 [meta] add npm run mocha for easier unit testing

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 flow-bin is breaking the build ๐Ÿšจ

Version 0.54.1 of flow-bin just got published.

Branch Build failing ๐Ÿšจ
Dependency flow-bin
Current Version 0.54.0
Type devDependency

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

As flow-bin 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
  • โœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details

Commits

The new version differs by 1 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 eslint-plugin-node is breaking the build ๐Ÿšจ

Version 4.1.0 of eslint-plugin-node just got published.

Branch Build failing ๐Ÿšจ
Dependency eslint-plugin-node
Current Version 4.0.1
Type devDependency

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

As eslint-plugin-node 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 passed Details

  • โŒ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes v4.1.0

New rules

  • c289f18 added no-hide-core-modules rule.
    This rule disallows require() expressions and import declarations if those import a third-party module which has the same name as core modules. Especially, if you depend on such modules indirectly and npm flattens dependencies, you can depend on such third-party modules before as you know it. This might cause unintentional behaviors.

Enhancements

Bug fixes

  • 17c8ae0 fixed the behavior of no-deprecated-api rule about indirect dependencies. The no-deprecated-api rule has ignored deprecated APIs if a code imports the third-party module which has same name as a core module. However, I found it can cause confusing because of indirect dependencies and flatting dependencies.
    Now, The no-deprecated-api rule does not ignore deprecated APIs even if a code imports the third-party module which has same name as a core module except it's in your package.json explicitly.
    If you want to revive old behavior, please set ignoreIndirectDependencies: true option.
Commits

The new version differs by 5 commits .

  • 3f03d92 4.1.0
  • c289f18 New: no-hide-core-modules (fixes #66)
  • 16973f9 Chore: hide a complexity warning.
  • 17c8ae0 Update: fix no-deprecated-api about modules which are hiding core modules (fixes #65)
  • 91ebdf4 Update: update no-unsupported-features for Node 7.6 supports async/await (fixes #67)

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 ๐Ÿšจ

The devDependency eslint-plugin-import was updated from 2.15.0 to 2.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-plugin-import 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/appveyor/branch: Waiting for AppVeyor build to complete (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.

  • 9bac44e bump to v2.16.0
  • d305f6a use proper rest arg instead of [].slice
  • e72a336 fix #1266 by moving closure creation out of parsing scope (#1275)
  • 1ec80fa Fix for #1256 (#1257)

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 eslint-plugin-import is breaking the build ๐Ÿšจ

The devDependency eslint-plugin-import was updated from 2.17.2 to 2.17.3.

๐Ÿšจ View failing branch.

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

eslint-plugin-import 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/appveyor/branch: AppVeyor build failed (Details).
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 25 commits.

  • cf5573b Bump to v2.17.3
  • caae65c [Tests] eslint 2 does not have linter.version
  • 557a3e2 [Deps] update resolve
  • 17beb33 Merge pull request #1356 from christophercurrie/typescript-declare
  • c8ac7ff [Docs] Document env option for eslint-import-resolver-webpack
  • c09c0ce Issue #1258 (docs)
  • 753c9db [refactor] fix eslint 6 compat by fixing imports
  • b52bf3e PR feedback
  • 7aa13d1 PR feedback
  • f66e064 Remove log messages
  • d1e4455 Verbose variable names
  • 67b1e95 Support older typescript parsers
  • 288cedf Make groups non-capturing.
  • aa290bb Improve support for Typescript declare structures
  • 1edbbd0 [Fix] no-common-js: Also throw an error when assigning

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 eslint-plugin-promise is breaking the build ๐Ÿšจ

The devDependency eslint-plugin-promise was updated from 4.0.1 to 4.1.0.

๐Ÿšจ View failing branch.

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

eslint-plugin-promise 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 is in progress (Details).
  • โŒ continuous-integration/appveyor/branch: AppVeyor 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 is breaking the build ๐Ÿšจ

Version 3.13.1 of eslint just got published.

Branch Build failing ๐Ÿšจ
Dependency eslint
Current Version 3.13.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 passed Details

  • โŒ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes v3.13.1
  • 3fc4e3f Fix: prefer-destructuring reporting compound assignments (fixes #7881) (#7882) (Teddy Katz)
  • f90462e Fix: no-extra-label autofix should not remove labels used elsewhere (#7885) (Teddy Katz)
Commits

The new version differs by 4 commits .

  • 7f8393c 3.13.1
  • 91883bf Build: package.json and changelog update for 3.13.1
  • 3fc4e3f Fix: prefer-destructuring reporting compound assignments (fixes #7881) (#7882)
  • f90462e Fix: no-extra-label autofix should not remove labels used elsewhere (#7885)

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 strip-ansi is breaking the build ๐Ÿšจ

The devDependency strip-ansi was updated from 5.0.0 to 5.1.0.

๐Ÿšจ View failing branch.

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

strip-ansi 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/appveyor/branch: Waiting for AppVeyor build to complete (Details).
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v5.1.0
  • Add support for terminal link escape codes (#26) 41b0a8b

v5.0.0...v5.1.0

Commits

The new version differs by 3 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 boxen is breaking the build ๐Ÿšจ

The dependency boxen was updated from 3.1.0 to 3.2.0.

๐Ÿšจ View failing branch.

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

boxen 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/appveyor/branch: Waiting for AppVeyor build to complete (Details).
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v3.2.0

v3.1.0...v3.2.0

Commits

The new version differs by 3 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 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 failed (Details).
  • โŒ continuous-integration/appveyor/branch: AppVeyor build failed (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 ๐ŸŒด

An in-range update of eslint-plugin-import is breaking the build ๐Ÿšจ

The devDependency eslint-plugin-import was updated from 2.17.0 to 2.17.1.

๐Ÿšจ View failing branch.

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

eslint-plugin-import 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/appveyor/branch: Waiting for AppVeyor build to complete (Details).
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 3 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 boxen is breaking the build ๐Ÿšจ

The dependency boxen was updated from 3.0.0 to 3.1.0.

๐Ÿšจ View failing branch.

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

boxen 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/appveyor/branch: Waiting for AppVeyor build to complete (Details).
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v3.1.0
  • Refactor TypeScript definition to CommonJS compatible export (#40) cb77ed1

v3.0.0...v3.1.0

Commits

The new version differs by 2 commits.

  • d566dd4 3.1.0
  • cb77ed1 Refactor TypeScript definition to CommonJS compatible export (#40)

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 eslint is breaking the build ๐Ÿšจ

Version 4.6.0 of eslint just got published.

Branch Build failing ๐Ÿšจ
Dependency eslint
Current Version 4.5.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
  • โœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details

Release Notes v4.6.0
  • 56dd769 Docs: fix link format in prefer-arrow-callback.md (#9198) (Vse Mozhet Byt)
  • 6becf91 Update: add eslint version to error output. (fixes #9037) (#9071) (่–›ๅฎš่ฐ”็š„็Œซ)
  • 0e09973 New: function-paren-newline rule (fixes #6074) (#8102) (Teddy Katz)
  • 88a64cc Chore: Make parseJsonConfig() a pure function in Linter (#9186) (Teddy Katz)
  • 1bbac51 Fix: avoid breaking eslint-plugin-eslint-comments (fixes #9193) (#9196) (Teddy Katz)
  • 3e8b70a Fix: off-by-one error in eslint-disable comment checking (#9195) (Teddy Katz)
  • 73815f6 Docs: rewrite prefer-arrow-callback documentation (fixes #8950) (#9077) (Charles E. Morgan)
  • 0d3a854 Chore: avoid mutating report descriptors in report-translator (#9189) (Teddy Katz)
  • 2db356b Update: no-unused-vars Improve message to include the allowed patterns (#9176) (Eli White)
  • 8fbaf0a Update: Add configurability to generator-star-spacing (#8985) (Ethan Rutherford)
  • 8ed779c Chore: remove currentScopes property from Linter instances (refs #9161) (#9187) (Teddy Katz)
  • af4ad60 Fix: Handle error when running init without npm (#9169) (Gabriel Aumala)
  • 4b94c6c Chore: make parse() a pure function in Linter (refs #9161) (#9183) (Teddy Katz)
  • 1be5634 Chore: don't make Linter a subclass of EventEmitter (refs #9161) (#9177) (Teddy Katz)
  • e95af9b Chore: don't include internal test helpers in npm package (#9160) (Teddy Katz)
  • 6fb32e1 Chore: avoid using private Linter APIs in astUtils tests (refs #9161) (#9173) (Teddy Katz)
  • de6dccd Docs: add documentation for Linter methods (refs #6525) (#9151) (Teddy Katz)
  • 2d90030 Chore: remove unused assignment. (#9182) (่–›ๅฎš่ฐ”็š„็Œซ)
  • d672aef Chore: refactor reporting logic (refs #9161) (#9168) (Teddy Katz)
  • 5ab0434 Fix: indent crash on sparse arrays with "off" option (fixes #9157) (#9166) (Teddy Katz)
  • c147b97 Chore: Make SourceCodeFixer accept text instead of a SourceCode instance (#9178) (Teddy Katz)
  • f127423 Chore: avoid using private Linter APIs in Linter tests (refs #9161) (#9175) (Teddy Katz)
  • 2334335 Chore: avoid using private Linter APIs in SourceCode tests (refs #9161) (#9174) (Teddy Katz)
  • 2dc243a Chore: avoid using internal Linter APIs in RuleTester (refs #9161) (#9172) (Teddy Katz)
  • d6e436f Fix: no-extra-parens reported some parenthesized IIFEs (fixes #9140) (#9158) (Teddy Katz)
  • e6b115c Build: Add an edit link to the rule docsโ€™ metadata (#9049) (Jed Fox)
  • fcb7bb4 Chore: avoid unnecessarily complex forEach calls in no-extra-parens (#9159) (Teddy Katz)
  • ffa021e Docs: quotes rule - when does \n require backticks (#9135) (avimar)
  • 60c5148 Chore: improve coverage in lib/*.js (#9130) (Teddy Katz)
Commits

The new version differs by 31 commits.

  • 8f01a99 4.6.0
  • c0acbf2 Build: changelog update for 4.6.0
  • 56dd769 Docs: fix link format in prefer-arrow-callback.md (#9198)
  • 6becf91 Update: add eslint version to error output. (fixes #9037) (#9071)
  • 0e09973 New: function-paren-newline rule (fixes #6074) (#8102)
  • 88a64cc Chore: Make parseJsonConfig() a pure function in Linter (#9186)
  • 1bbac51 Fix: avoid breaking eslint-plugin-eslint-comments (fixes #9193) (#9196)
  • 3e8b70a Fix: off-by-one error in eslint-disable comment checking (#9195)
  • 73815f6 Docs: rewrite prefer-arrow-callback documentation (fixes #8950) (#9077)
  • 0d3a854 Chore: avoid mutating report descriptors in report-translator (#9189)
  • 2db356b Update: no-unused-vars Improve message to include the allowed patterns (#9176)
  • 8fbaf0a Update: Add configurability to generator-star-spacing (#8985)
  • 8ed779c Chore: remove currentScopes property from Linter instances (refs #9161) (#9187)
  • af4ad60 Fix: Handle error when running init without npm (#9169)
  • 4b94c6c Chore: make parse() a pure function in Linter (refs #9161) (#9183)

There are 31 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 ๐Ÿšจ

The devDependency eslint-plugin-import was updated from 2.14.0 to 2.15.0.

๐Ÿšจ View failing branch.

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

eslint-plugin-import 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 is in progress (Details).
  • โŒ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

Commits

The new version differs by 34 commits.

  • 767f01a bump to v2.15.0
  • 038d668 bump webpack resolver to v0.11.0
  • 20a8f3b bump utils to v2.3.0
  • 1e4100d changelog note for #1261
  • 548ea02 added support for argv parameter of webpack`s config-as-a-function (#1261)
  • fcf2ce7 Merge pull request #1254 from ljharb/travis
  • 64d9be7 allow_failures for dicey Node/ESLint intersection
  • 73080d0 dep-time-travel: use older versions of dependencies
  • 05c3935 repair no-deprecated for ESLint* 5
  • 10c9811 node 4 fix for test util
  • f165237 ah geez, bumping babel-eslint breaks no-amd/no-cjs
  • acfb6e9 jk, test against eslint 2/3 but skip Typescript tests.
  • b686f9d drop ESLint 2/3 from Travis/Appveyor
  • cf1f6f4 [Deps] update debug, eslint-import-resolver-node, has, lodash, minimatch, resolve
  • d290a87 [Dev Deps] update babylon, coveralls, eslint-import-resolver-typescript, gulp, linklocal, nyc, redux, rimraf, sinon, typescript-eslint-parser

There are 34 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 eslint-plugin-promise is breaking the build ๐Ÿšจ

The devDependency eslint-plugin-promise was updated from 4.1.1 to 4.2.1.

๐Ÿšจ View failing branch.

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

eslint-plugin-promise 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/appveyor/branch: Waiting for AppVeyor build to complete (Details).
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 6 commits.

  • 5b935bd 4.2.1
  • 9017a70 4.2.1
  • 254c0fd 4.2.0
  • 3f2c61d Merge pull request #136 from ota-meshi/fix/no-return-wrap
  • 57267ca Add testcase
  • d8b9206 Fixed that no-return-wrap does not work if type is not "ExpressionStatement".

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 flow-bin is breaking the build ๐Ÿšจ

Version 0.37.4 of flow-bin just got published.

Branch Build failing ๐Ÿšจ
Dependency flow-bin
Current Version 0.37.3
Type devDependency

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

As flow-bin 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 passed Details

  • โŒ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 1 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 ๐ŸŒด

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.