Light

jokeyrhyme / argv-auto-glob.js Goto Github PK

View Code? Open in Web Editor NEW

1.0 1.0 0.0 171 KB

automatically expand globs (cross-platform) for the `process.argv` array (or similar)

License: MIT License

JavaScript 100.00%

argv-auto-glob.js's People

Contributors

Stargazers

Watchers

argv-auto-glob.js's Issues

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

Version 2.12.0 of eslint-plugin-import was just published.

Branch	Build failing 🚨
Dependency	`eslint-plugin-import`
Current Version	2.11.0
Type	devDependency

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 could not complete due to an error Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 33 commits.

8f668c7 changelog/package bumps
cd9d249 exclude tests from coverage + bump TS parser (#1095)
f0d0c4f webpack resolver: cache instance(s) of resolve function (#1091)
8c9c3b8 Merge pull request #1085 from benmosher/packageDir-array
5111c79 revert has removal per @ljharb's note
412ee2e [Refactor] use "has" instead of ".hasOwnProperty"
e2fdc5f Fix typo: 'runtime'
d8ca5e2 fix typo
04d1c29 Merge branch 'master' into packageDir-array
72bb2cb merge import/paths setting into existing packageDir option
4e37dbf changelog links
2e41a70 Merge pull request #1081 from benmosher/release
2e0ed83 Merge branch 'master' into release
ec87b64 Ignore type imports for named rule. (#1057)
d5d8b35 memo-parser cautionary note

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

Version 11.2.0 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	11.1.0
Type	devDependency

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

As nyc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ 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 7 commits.

b2ff72d chore(release): 11.2.0
97b962e chore: explicit update of istanbul-lib-instrument (#662)
0dcceda feat: allow cwd to be configured see #620
0fc6d8f chore: add support for --cwd (#542) (#620)
658dba4 fix: remove excluded files from coverage before writing (#649)
dd40dc5 feat: add possibility to filter coverage-maps (#637)
fb3ab92 docs: add link to community slack (#639)

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/appveyor/branch: AppVeyor build failed (Details).
❌ continuous-integration/travis-ci/push: The Travis CI build is in progress (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 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 failed 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.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/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 3 commits.

b0c5e1a bump to v2.17.1
f6716ad [fix] require v2.4 of eslint-module-utils
5124dde [utils] v2.4.0

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

The dependency glob was updated from `7.1.3` to `7.1.4`.

🚨 View failing branch.

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

glob 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 is in progress (Details).
❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

Commits

The new version differs by 5 commits.

2da9af3 7.1.4
28c2237 Add logo to license
92923a6 website link
17cf014 png vs svg
0af8a58 adding the globby

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

The dependency glob was updated from `7.1.5` to `7.1.6`.

🚨 View failing branch.

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

glob 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).
❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

Commits

The new version differs by 3 commits.

f5a57d3 7.1.6
9d415a9 add funding
11b7dcc add funding

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.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: AppVeyor build failed (Details).
❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (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 🌴

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 🚨

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.12.1 of eslint was just published.

Branch	Build failing 🚨
Dependency	eslint
Current Version	4.12.0
Type	devDependency

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 passed Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

v4.12.1

1e362a0 Revert "Fix: Use XML 1.1 on XML formatters (fixes #9607) (#9608)" (#9667) (Kevin Partington)

Commits

The new version differs by 3 commits.

58216b6 4.12.1
fc9d27b Build: changelog update for 4.12.1
1e362a0 Revert "Fix: Use XML 1.1 on XML formatters (fixes #9607) (#9608)" (#9667)

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

Version 7.1.3 of glob was just published.

Branch	Build failing 🚨
Dependency	glob
Current Version	7.1.2
Type	dependency

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

glob 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).
❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

Commits

The new version differs by 3 commits.

8882c8f 7.1.3
d1bf951 bump tap
b93889c Fix win32 test failure

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

Version 11.8.0 of nyc was just published.

Branch	Build failing 🚨
Dependency	`nyc`
Current Version	11.7.3
Type	devDependency

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 could not complete due to an error Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 2 commits.

bc9ffe5 chore(release): 11.8.0
9def3eb feat: merge together multiple istanbul format reports (#840)

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.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/travis-ci/push The Travis CI build failed Details
❌ continuous-integration/appveyor/branch AppVeyor 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 nyc is breaking the build 🚨

Version 11.2.1 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
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 nyc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 3 commits.

87281f9 chore(release): 11.2.1
3bd1527 fix: create temp directory when --no-clean flag is set #663 (#664)
a10d478 fix: apply exclude logic before remapping coverage (#667)

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/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 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 could not complete due to an error (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 🚨

Version 3.8.0 of eslint-plugin-promise was just published.

Branch	Build failing 🚨
Dependency	`eslint-plugin-promise`
Current Version	3.7.0
Type	devDependency

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 could not complete due to an error Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 9 commits.

67dad97 3.8.0
212e557 docs(changelog): prepare for v3.8.0 (#132)
9b0cbd1 refactor: lookup promise statics from object instead of array (#131)
ceb7414 feat: turn off avoid-new in recommended configuration (#119)
b5a6423 chore(package): add package-lock.json (#130)
4ebd2c6 fix: ignore event listener callbacks in prefer-await-to-callbacks (#117)
4a3d5b8 fix: ignore top-level awaits in prefer-await-to-then (#126)
0b231da docs: add no-nesting examples (#120)
5956eca docs: add examples to prefer-await-to-then (#121)

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/appveyor/branch AppVeyor build failed Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 1 commits.

4ece6ed v0.54.1

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.13.0 of eslint-plugin-import was just published.

Branch	Build failing 🚨
Dependency	`[eslint-plugin-import](https://github.com/benmosher/eslint-plugin-import)`
Current Version	2.12.0
Type	devDependency

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 could not complete due to an error Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 7 commits.

c34f14f changelog/package bumps
9db789b [Fix] namespace: ensure this rule works in ES2018
add69cf [New] Add ESLint 5 support
59fc04e [Tests] on node v10
cdb328c [webpack] log a useful error in a module bug arises
ebafcbf no-restricted-paths: complete coverage
e6f5c13 No relative parent imports rule (#1093)

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

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

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

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

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
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.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

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

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.