Giter Site home page Giter Site logo

benmvp / benmvp-cli Goto Github PK

View Code? Open in Web Editor NEW
21.0 4.0 2.0 2.51 MB

A highly-opinionated, zero-config CLI for consistent infra for Ben Ilegbodu's Typescript-based libraries

License: MIT License

JavaScript 7.08% TypeScript 88.16% Shell 4.76%
cli unit-test typescript benmvp umd esm code-coverage

benmvp-cli's People

Contributors

benmvp avatar dependabot[bot] avatar greenkeeper[bot] avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

benmvp-cli's Issues

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

There have been updates to the babel7 monorepo:

    • The dependency @babel/cli was updated from 7.8.0 to 7.8.3.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 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
  • ❌ Test (Node 13): There are 1 failures, 0 warnings, and 0 notices.
  • ❌ Format files: There are 1 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 12): There are 2 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 10): There are 1 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 8): There are 1 failures, 0 warnings, and 0 notices.

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 🌴

Move CJS build to to root

πŸš€ Feature Proposal

Instead of putting the CJS build at lib/cjs, put it at lib/ so that it'll be at the root of the package. The esm/ folder will remain.

Motivation

This allows the package to do deep importing without having to reference the cjs/ folder.

Example

We want this:

import { getValue } from 'my-lib/getters'

Instead of:

import { getValue } from 'my-lib/cjs/getters'

Action required: Greenkeeper could not be activated 🚨

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

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

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

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

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

The devDependency @types/yargs was updated from 12.0.2 to 12.0.3.

🚨 View failing branch.

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

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

The dependency eslint-plugin-jest was updated from 22.5.1 to 22.6.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-jest 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).

Release Notes for v22.6.0

22.6.0 (2019-05-22)

Features

Commits

The new version differs by 9 commits.

  • 14d83ef feat(rules): add no-commented-out rule (#262)
  • 83ff198 chore: migrate no-jest-import to typescript (#259)
  • 718c08c chore: upgrade @typescript-eslint
  • ca2aa27 chore: port lowercase-name to TypeScript (#258)
  • 3df0058 chore(ci): run danger with lts version of node
  • 48e3a59 chore: precompile with babel (#257)
  • 8670804 chore: bump deps
  • 05eb11a chore: fix lint error
  • dff6446 docs: link to eslint-plugin-jest-formatting

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 @typescript-eslint/parser is breaking the build 🚨

The dependency @typescript-eslint/parser was updated from 2.17.0 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.

@typescript-eslint/parser 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
  • ❌ Test (Node 13): There are 1 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 12): There are 2 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 10): There are 2 failures, 0 warnings, and 0 notices.
  • βœ… Format files: null
  • ❌ Test (Node 8): There are 2 failures, 0 warnings, and 0 notices.

Release Notes for v2.18.0

2.18.0 (2020-01-27)

Bug Fixes

  • eslint-plugin: [explicit-module-boundary-types] false positive for returned fns (#1490) (5562ad5)
  • improve token types and add missing type guards (#1497) (ce41d7d)
  • eslint-plugin: [naming-convention] fix filter option (#1482) (718cd88)
  • eslint-plugin: fix property access on undefined error (#1507) (d89e8e8)
  • experimental-utils: widen type of settings property (#1527) (b515e47)
  • typescript-estree: error on unexpected jsdoc nodes (#1525) (c8dfac3)
  • typescript-estree: fix identifier tokens typed as Keyword (#1487) (77a1caa)

Features

  • eslint-plugin: add comma-spacing (#1495) (1fd86be)
  • eslint-plugin: add new rule prefer-as-const (#1431) (420db96)
  • eslint-plugin: create ban-ts-comment rule (#1361) (2a83d13)
  • eslint-plugin-internal: add prefer-ast-types-enum (#1508) (c3d0a3a)
  • experimental-utils: make RuleMetaData.docs optional (#1462) (cde97ac)
  • parser: improve scope-analysis types (#1481) (4a727fa)
Commits

The new version differs by 30 commits.

  • b835ec2 chore: publish v2.18.0
  • 367b18f docs(eslint-plugin): add script to generate the readme tables (#1524)
  • 03221d2 test: fix vscode launch configuration for windows (#1523)
  • f991764 chore(eslint-plugin): refactor explicit return type rules to share code (#1493)
  • c8dfac3 fix(typescript-estree): error on unexpected jsdoc nodes (#1525)
  • 6d1d2a2 test: fix coverage reports from codecov (#1528)
  • b515e47 fix(experimental-utils): widen type of settings property (#1527)
  • 67784d6 docs: extra 'a' in CONTRIBUTING.md (#1518)
  • afa7900 chore: enable prefer-ast-types-enum internal rule (#1514)
  • c3d0a3a feat(eslint-plugin-internal): add prefer-ast-types-enum (#1508)
  • 718cd88 fix(eslint-plugin): [naming-convention] fix filter option (#1482)
  • 802e347 chore(eslint-plugin): use getFixturesRootDir in tests (#1506)
  • 9ca65dc chore: update istanbul-reports to make tests quiet (#1509)
  • d89e8e8 fix(eslint-plugin): fix property access on undefined error (#1507)
  • 06731e7 test(eslint-plugin): cleanup no-use-before-define tests (#1505)

There are 30 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 jest-runner-eslint is breaking the build 🚨

The dependency jest-runner-eslint was updated from 0.7.5 to 0.7.6.

🚨 View failing branch.

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

jest-runner-eslint 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
  • ❌ Test (Node 13): There are 1 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 12): null
  • ❌ Test (Node 10): null
  • ❌ Test (Node 8): null
  • βœ… Format files: null

Commits

The new version differs by 5 commits.

  • d09d788 0.7.6
  • 39d96c0 feat: upgrade jest to v25 (#83)
  • 8f45e34 Bump handlebars from 4.1.2 to 4.5.3 in /examples/simple (#81)
  • fc12d20 Bump handlebars from 4.1.2 to 4.5.3 (#80)
  • f14556b chore: docs - correct default value for β€˜quiet’ (#79)

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

The dependency @types/node was updated from 12.6.9 to 12.7.0.

🚨 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 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 🌴

Action required: Greenkeeper could not be activated 🚨

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

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

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

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

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

There have been updates to the react monorepo:

    • The devDependency react was updated from 16.12.0 to 16.13.0.
  • The devDependency react-dom was updated from 16.12.0 to 16.13.0.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the react group definition.

react 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
  • βœ… Format files: null
  • ❌ Test (Node 13): There are 1 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 12): There are 2 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 10): There are 2 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 8): There are 2 failures, 0 warnings, and 0 notices.

Release Notes for 16.13.0 (February 26, 2020)

React

  • Warn when a string ref is used in a manner that's not amenable to a future codemod (@lunaruan in #17864)
  • Deprecate React.createFactory() (@trueadm in #17878)

React DOM

Concurrent Mode (Experimental)

Artifacts

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/fs-extra is breaking the build 🚨

The devDependency @types/fs-extra was updated from 8.0.1 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.

@types/fs-extra 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
  • ❌ Test (Node 13): null
  • ❌ Test (Node 12): There are 1 failures, 0 warnings, and 0 notices.
  • βœ… Format files: null
  • ❌ Test (Node 10): null
  • ❌ Test (Node 8): null

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

The dependency @typescript-eslint/eslint-plugin was updated from 1.9.0 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.

@typescript-eslint/eslint-plugin 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 @testing-library/react is breaking the build 🚨

The dependency @testing-library/react was updated from 9.4.0 to 9.4.1.

🚨 View failing branch.

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

@testing-library/react 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
  • βœ… Format files: null
  • ❌ Test (Node 13): There are 1 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 12): null
  • ❌ Test (Node 10): There are 2 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 8): There are 2 failures, 0 warnings, and 0 notices.

Release Notes for v9.4.1

9.4.1 (2020-02-22)

Bug Fixes

  • release: manually release a patch version (c4cae93)
  • make fireEvent mouseEnter/mouseLeave work with addEventListener (#588) (c5a7206), closes #577 #577
Commits

The new version differs by 10 commits.

  • c4cae93 fix(release): manually release a patch version
  • 41c01c8 docs: add zbrogz as a contributor (#592)
  • c5a7206 fix: make fireEvent mouseEnter/mouseLeave work with addEventListener (#588)
  • 24fc9b0 chore: update issue templates
  • b8855b5 chore: fix all contributors config
  • d6fac05 chore: update all the deps
  • 7e2dac4 docs: add tteke as a contributor (#574)
  • cd3edf4 docs: fix error on complex example (#560)
  • 8db62fe docs: add sakito21 as a contributor (#554)
  • e6ff3b8 docs: use screen (#553)

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

The devDependency @types/node was updated from 11.10.4 to 11.10.5.

🚨 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 @typescript-eslint/parser is breaking the build 🚨

The dependency @typescript-eslint/parser was updated from 1.9.0 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.

@typescript-eslint/parser 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 @types/jest is breaking the build 🚨

The dependency @types/jest was updated from 24.0.19 to 24.0.20.

🚨 View failing branch.

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

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

The dependency eslint-plugin-jest was updated from 23.6.0 to 23.7.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-jest 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
  • ❌ Test (Node 13): There are 2 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 12): There are 1 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 10): There are 2 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 8): There are 2 failures, 0 warnings, and 0 notices.
  • βœ… Format files: null

Release Notes for v23.7.0

23.7.0 (2020-02-07)

Bug Fixes

Features

  • valid-title: support disallowedWords option (#522) (38bbe93)
Commits

The new version differs by 7 commits.

  • 88068a7 chore(release): 23.7.0 [skip ci]
  • c12b725 fix(expect-expect): use u flag in regex (#532)
  • ff25588 chore(deps): removed dependency on micromatch for expect-expect (#517)
  • 38bbe93 feat(valid-title): support disallowedWords option (#522)
  • 1449675 chore: make gh actions badge always point to master
  • 95cce6b chore(deps): lock file maintenance (#490)
  • 735f143 chore(lint): enable require-unicode-regexp rule (#520)

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

The dependency eslint-plugin-jest was updated from 22.3.0 to 22.3.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-jest 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 v22.3.1

22.3.1 (2019-03-12)

Bug Fixes

  • no-identical-title: not reporting when using backticks (#237) (4f8ef6d), closes #232
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 🌴

Add tests for build command

We should add tests for build/index.ts just like we have them for test/index.ts & start/index.ts. Will need to mock runBabel and execSync

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


☝️ Important announcement: Greenkeeper will be saying goodbye πŸ‘‹ and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The dependency eslint-plugin-prettier was updated from 3.1.2 to 3.1.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-prettier 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
  • ❌ Test (Node 13): null
  • ❌ Test (Node 12): null
  • ❌ Test (Node 10): null
  • ❌ Test (Node 8): There are 1 failures, 0 warnings, and 0 notices.
  • βœ… Format files: null

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

The dependency yargs was updated from 15.1.0 to 15.2.0.

🚨 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
  • ❌ Test (Node 13): null
  • ❌ Test (Node 12): There are 1 failures, 0 warnings, and 0 notices.
  • βœ… Format files: null
  • ❌ Test (Node 10): null
  • ❌ Test (Node 8): null

Release Notes for yargs v15.2.0

⚠ BREAKING CHANGES

  • deps: [email protected] no longer implicitly creates arrays out of boolean
    arguments when duplicates are provided

Features

Bug Fixes

  • help always displayed for the first command parsed having an async handler (#1535) (d585b30)
  • deps: fix enumeration for normalized path arguments (#1567) (0b5b1b0)
  • locales: only translate default option group name (acc16de)
  • locales: remove extra space in French for 'default' (#1564) (ecfc2c4)
  • translations: add French translation for unknown command (#1563) (18b0b75)
  • translations: fix pluralization in error messages. (#1557) (94fa38c)
  • yargs: correct support of bundled electron apps (#1554) (a0b61ac)
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-react-hooks is breaking the build 🚨

The dependency eslint-plugin-react-hooks was updated from 2.3.0 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.

eslint-plugin-react-hooks 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
  • ❌ Test (Node 13): There are 2 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 12): There are 2 failures, 0 warnings, and 0 notices.
  • βœ… Format files: null
  • ❌ Test (Node 10): There are 1 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 8): There are 2 failures, 0 warnings, and 0 notices.

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

The dependency eslint-config-prettier was updated from 6.9.0 to 6.10.0.

🚨 View failing branch.

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

eslint-config-prettier 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
  • ❌ Test (Node 13): There are 2 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 12): There are 2 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 10): There are 2 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 8): There are 1 failures, 0 warnings, and 0 notices.
  • βœ… Format files: null

Commits

The new version differs by 4 commits.

  • 95a476e eslint-config-prettier v6.10.0
  • b7e3e90 Update npm packages
  • 04c79bf Disable @typescript-eslint/comma-spacing (#135)
  • d89bb10 Bump eslint from 6.6.0 to 6.8.0 (#136)

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

The dependency jest-enzyme was updated from 7.1.1 to 7.1.2.

🚨 View failing branch.

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

jest-enzyme 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 11 commits ahead by 11, behind by 2.

  • abce48f v7.1.2
  • 7951364 Changelog 7.1.2
  • 8697d81 Use setupFilesAfterEnv instead of setupTestFrameworkScriptFile
  • ffb2861 Add second type parameter
  • 4e18cb1 Update packages/jest-enzyme/README.md, add changes suggestion.
  • 9253e39 Update README.md: fix a link to #tohavedisplayname.
  • 271af50 Upgrade Babel to 7.6.2 and Jest to 24.9.0
  • 5556aa6 Replace setupTestFrameworkScriptFile with setupFilesAfterEnv in jest-environment-enzyme README.md
  • 54dbf3c Replace setupTestFrameworkScriptFile with setupFilesAfterEnv in jest-enzyme README.md
  • 66c1937 v7.1.1
  • 427710d 7.1.1 Changelog

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

The dependency @typescript-eslint/eslint-plugin was updated from 2.17.0 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.

@typescript-eslint/eslint-plugin 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
  • ❌ Test (Node 13): There are 2 failures, 0 warnings, and 0 notices.
  • ❌ Format files: There are 1 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 12): There are 1 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 10): There are 1 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 8): There are 1 failures, 0 warnings, and 0 notices.

Release Notes for v2.18.0

2.18.0 (2020-01-27)

Bug Fixes

  • eslint-plugin: [explicit-module-boundary-types] false positive for returned fns (#1490) (5562ad5)
  • improve token types and add missing type guards (#1497) (ce41d7d)
  • eslint-plugin: [naming-convention] fix filter option (#1482) (718cd88)
  • eslint-plugin: fix property access on undefined error (#1507) (d89e8e8)
  • experimental-utils: widen type of settings property (#1527) (b515e47)
  • typescript-estree: error on unexpected jsdoc nodes (#1525) (c8dfac3)
  • typescript-estree: fix identifier tokens typed as Keyword (#1487) (77a1caa)

Features

  • eslint-plugin: add comma-spacing (#1495) (1fd86be)
  • eslint-plugin: add new rule prefer-as-const (#1431) (420db96)
  • eslint-plugin: create ban-ts-comment rule (#1361) (2a83d13)
  • eslint-plugin-internal: add prefer-ast-types-enum (#1508) (c3d0a3a)
  • experimental-utils: make RuleMetaData.docs optional (#1462) (cde97ac)
  • parser: improve scope-analysis types (#1481) (4a727fa)
Commits

The new version differs by 30 commits.

  • b835ec2 chore: publish v2.18.0
  • 367b18f docs(eslint-plugin): add script to generate the readme tables (#1524)
  • 03221d2 test: fix vscode launch configuration for windows (#1523)
  • f991764 chore(eslint-plugin): refactor explicit return type rules to share code (#1493)
  • c8dfac3 fix(typescript-estree): error on unexpected jsdoc nodes (#1525)
  • 6d1d2a2 test: fix coverage reports from codecov (#1528)
  • b515e47 fix(experimental-utils): widen type of settings property (#1527)
  • 67784d6 docs: extra 'a' in CONTRIBUTING.md (#1518)
  • afa7900 chore: enable prefer-ast-types-enum internal rule (#1514)
  • c3d0a3a feat(eslint-plugin-internal): add prefer-ast-types-enum (#1508)
  • 718cd88 fix(eslint-plugin): [naming-convention] fix filter option (#1482)
  • 802e347 chore(eslint-plugin): use getFixturesRootDir in tests (#1506)
  • 9ca65dc chore: update istanbul-reports to make tests quiet (#1509)
  • d89e8e8 fix(eslint-plugin): fix property access on undefined error (#1507)
  • 06731e7 test(eslint-plugin): cleanup no-use-before-define tests (#1505)

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

The dependency eslint-plugin-import was updated from 2.20.0 to 2.20.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 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
  • ❌ Test (Node 13): null
  • ❌ Test (Node 12): There are 1 failures, 0 warnings, and 0 notices.
  • βœ… Format files: null
  • ❌ Test (Node 10): There are 2 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 8): null

Commits

The new version differs by 23 commits.

  • 45f0860 Bump to v2.20.1
  • 5d00854 [Fix] order: Fix alphabetize for mixed requires and imports
  • bbd166b [Fix] export: Handle function overloading in *.d.ts
  • 4665ec5 [Fix] no-absolute-path: fix a crash with invalid import syntax
  • 392c6b9 [Fix] named: for importing from a module which re-exports named exports from a node_modules module
  • cc5bde5 [Tests] named: add failing test for #1446
  • aff3a46 [meta] fix "files" field to include/exclude the proper files
  • 986ba74 docs: fix a few spelling mistakes
  • 6274d96 [Tests] set eslint-plugin/consistent-output lint rule to always require test case output assertions
  • a4d301b [meta] add missing changelog links
  • 2d42464 [Tests] only run the linter once, not on every build
  • 26f232b [Tests] add eslint-plugin-eslint-plugin internally and fix violations
  • 99647f1 [Docs]: Update Tidelift language to enterprise
  • f84d457 no-duplicates: allow duplicate if one is namespace and other not
  • 7e71b50 [Fix] extensions: Fix scope regex

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 jest-environment-enzyme is breaking the build 🚨

The dependency jest-environment-enzyme was updated from 7.1.1 to 7.1.2.

🚨 View failing branch.

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

jest-environment-enzyme 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 11 commits ahead by 11, behind by 2.

  • abce48f v7.1.2
  • 7951364 Changelog 7.1.2
  • 8697d81 Use setupFilesAfterEnv instead of setupTestFrameworkScriptFile
  • ffb2861 Add second type parameter
  • 4e18cb1 Update packages/jest-enzyme/README.md, add changes suggestion.
  • 9253e39 Update README.md: fix a link to #tohavedisplayname.
  • 271af50 Upgrade Babel to 7.6.2 and Jest to 24.9.0
  • 5556aa6 Replace setupTestFrameworkScriptFile with setupFilesAfterEnv in jest-environment-enzyme README.md
  • 54dbf3c Replace setupTestFrameworkScriptFile with setupFilesAfterEnv in jest-enzyme README.md
  • 66c1937 v7.1.1
  • 427710d 7.1.1 Changelog

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

The devDependency @types/jest was updated from 24.0.9 to 24.0.10.

🚨 View failing branch.

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

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

The dependency eslint-plugin-react was updated from 7.18.0 to 7.18.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-react 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
  • βœ… Format files: null
  • ❌ Test (Node 13): There are 1 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 12): There are 2 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 10): null
  • ❌ Test (Node 8): null

Commits

The new version differs by 9 commits.

  • 000d6b8 Update CHANGELOG and bump version
  • ffdf69a [Fix] jsx-indent: Does not check indents for JSXText
  • 182b045 [Docs] use markdown-magic to automatically sort all rules alphabetically
  • 45b9d32 [Docs] jsx-props-no-spreading: fix typo to use correct rule
  • f9aee94 [Fix] jsx-props-no-spreading: add support for namespaced jsx components
  • e69b113 [Fix] jsx-no-target-blank: allow rel to be an expression
  • fc6e406 [meta] fix changelog date
  • 50df78f [Fix] sort-comp: | isn’t a valid regex flag; u and s are
  • a7f6a8b [Tests] on node v13

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


☝️ Important announcement: Greenkeeper will be saying goodbye πŸ‘‹ and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The devDependency @types/lodash was updated from 4.14.149 to 4.14.150.

🚨 View failing branch.

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

@types/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
  • βœ… Format files: null
  • ❌ Test (Node 13): There are 2 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 12): There are 1 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 10): There are 2 failures, 0 warnings, and 0 notices.
  • βœ… Test (Node 8): null

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


☝️ Important announcement: Greenkeeper will be saying goodbye πŸ‘‹ and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The dependency eslint-config-airbnb was updated from 18.0.1 to 18.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-config-airbnb 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
  • ❌ Test (Node 13): There are 1 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 12): There are 2 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 10): There are 2 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 8): There are 2 failures, 0 warnings, and 0 notices.
  • βœ… Format files: null

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 dependency @types/node was updated from 13.5.0 to 13.5.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 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
  • ❌ Test (Node 13): There are 1 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 12): There are 2 failures, 0 warnings, and 0 notices.
  • ❌ Test (Node 10): There are 2 failures, 0 warnings, and 0 notices.
  • βœ… Format files: null
  • ❌ Test (Node 8): There are 2 failures, 0 warnings, and 0 notices.

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 🌴

React warning when running tests in non-React lib

πŸ› Bug Report

When running npm test within url-lib, I get the following warning:

Warning: React version was set to "detect" in eslint-plugin-react settings, but the "react" package is not installed. Assuming latest React version for linting.

The tests still pass, but the warning clutters the console and is quite confusing seeing as how url-lib doesn't have react at all.

To Reproduce

  1. Clone url-lib
  2. npm install
  3. npm test -- --modes lint

You'll see multiples of the warning messages.

Expected behavior

The warning messages wouldn't show. And technically speaking the plugin really only should be used for React-based libs

Link to repl or repo (highly encouraged)

See above

envinfo

  System:
    OS: macOS Mojave 10.14.6
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 2.77 GB / 32.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 12.14.0 - ~/.nvm/versions/node/v12.14.0/bin/node
    Yarn: 1.19.1 - /usr/local/bin/yarn
    npm: 6.13.4 - ~/.nvm/versions/node/v12.14.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman

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.