Giter VIP home page Giter VIP logo

spellbook's People

Contributors

brandonocasey avatar greenkeeper[bot] avatar

Stargazers

 avatar

Watchers

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

spellbook's Issues

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

Version 7.8.0 of stylelint just got published.

Branch Build failing 🚨
Dependency stylelint
Current Version 7.7.1
Type dependency

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

As stylelint is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes 7.8.0
  • Deprecated: 15 rules (#2197, #2285 & #2309).
    • block-no-single-line. Use block-opening-brace-newline-after and block-closing-brace-newline-before rules with the option "always" instead.
    • declaration-block-properties-order. Use the stylelint-order plugin pack instead.
    • rule-nested-empty-line-before and rule-non-nested-empty-line-before. Use the new rule-empty-line-before rule instead.
    • time-no-imperceptible. Use the new time-min-milliseconds rule with 100 as its primary option.
    • It is beyond the scope of stylelint's core package to effectively validate against the CSS spec. Please investigate csstree and css-values for this functionality, and contribute to those projects and to stylelint plugins wrapping them. csstree already has a stylelint plugin, and css-values needs one to be developed. The following rules are deprecated for this reason.
      • media-feature-no-missing-punctuation.
      • selector-no-empty.
    • A plugin is a better package for a rule that wraps a third-party library. The following rules are deprecated for this reason. We encourage users to create and help maintain plugins for these rules.
      • no-browser-hacks
      • no-indistinguishable-colors
      • no-unsupported-browser-features
    • The following rules did not seem useful. If you liked these rules, please create plugins for them.
      • custom-property-no-outside-root
      • root-no-standard-properties
      • selector-root-no-composition.
    • The following rules did not work well.
      • stylelint-disable-reason. Please consider contributing to #2292 for a replacement.
      • declaration-block-no-ignored-properties could not reliably account for replaced elements.
  • Deprecated: 4 options (#2213).
    • "all-nested" option for at-rule-empty-line-before. Use the "inside-block" option instead.
    • "blockless-group" option for at-rule-empty-line-before. Use the "blockless-after-blockless" option instead.
    • "between-comments" option for comment-empty-line-before. Use the "after-comment" option instead.
    • "at-rules-without-declaration-blocks" option for max-nesting-depth. Use the "blockless-at-rules" option instead.
  • Added: time-min-milliseconds rule, to replace time-no-imperceptible (#2289).
  • Added: except: ["after-same-name"] option to at-rule-empty-line-before (#2225).
  • Fixed: configOverrides now work with extends (#2295).
  • Fixed: max-line-length no longer reports incorrect column positions for lines with url() or import (#2287).
  • Fixed: selector-pseudo-class-no-unknown no longer warns for proprietary webkit pseudo-classes (#2264).
  • Fixed: unit-no-unknown accepts fr units (#2308).
Commits

The new version differs by 42 commits .

  • b56306d Prepare 7.8.0
  • 8b2c7fb Update changelog
  • 06943a4 Add rule-empty-line-before rule (#2309)
  • 3c76452 Put back links to deprecated rules (#2313)
  • 6ab2c26 Use HTTPS links where applicable. (#2311)
  • e484170 Prepare CHANGELOG and release planning (#2299)
  • a84596e Update CHANGELOG.md
  • a36c94c Add fr to known units (#2308)
  • 16014e1 Remove tape testRule leftover (#2306)
  • e28566c Use fenced code blocks
  • 2b68f31 Use https://stylelint.io everywhere
  • 3888238 Standardise deprecation notes and warnings (#2300)
  • 830221f Improve documentation of "always-multi-line" in at-rule-name-newline-after (#2304)
  • 09955dd Revert deprecation of stylelint-commands option (#2302)
  • 7aa2282 Deprecate rules (#2197) (#2298)

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

Version 3.5.1 of bluebird just got published.

Branch Build failing 🚨
Dependency bluebird
Current Version 3.5.0
Type dependency

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

bluebird is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.5.1

Bugfixes:

  • Fix false positive unhandled rejection when using async await (#1404)
  • Fix false positive when reporting error as non-error (#990)
Commits

The new version differs by 26 commits.

  • dcfa52b Release v3.5.1
  • 48c8591 Fixes #1404
  • 3c93a91 Revert "Update default.html"
  • 5155a7b Merge pull request #1463 from gabegorelick/isError
  • 3f7ccf4 Better error check
  • f8f4a01 Merge pull request #1462 from themez/patch-1
  • 18891c9 Fix title style
  • b2b14c2 Update default.html
  • a61aa1c tiny grammar change (#1457)
  • 2c9f7a4 Update tap.md (#1438)
  • 3a7fcbb fixes markdow headers (#1437)
  • e889c0d Correct a tiny tiny typo (#1431)
  • e03f12c improve .all() docs (#1436)
  • 4f90934 Updated links (#1420)
  • 3d2e57f Add Node.js 7+8 to Travis build matrix (#1412)

There are 26 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 🌴

Is there a way to use custom eslint config files?

I want to use some ecmaVersion 8 syntax in a plugin and linting fails on that line because the current eslint rulesheet is pegged at version 6 - is it possible to use custom eslint config files with sb-lint options?

Run lint with test

  • Run sb-lint (nonFatally when test is run in non-watch mode)
  • Fail test if linting fails, but after tests are run
  • Don't run sb-lint in watch mode for tests

An in-range update of node-sass is breaking the build 🚨

Version 4.5.1 of node-sass just got published.

Branch Build failing 🚨
Dependency node-sass
Current Version 4.5.0
Type dependency

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

As node-sass is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes v4.5.1

Fixes


Supported Environments

OS Architecture Node
Windows x86 & x64 0.10, 0.12, 1, 2, 3, 4, 5, 6,7
OSX x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7
Linux* x86 & x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7
Alpine x64 4, 6, 7

*Linux support refers to Ubuntu, Debian, and CentOS 5

Commits

The new version differs by 10 commits .

  • f2b410b Update changelog
  • 86c600a 4.5.1
  • b0147a8 Merge pull request #1929 from xzyfer/support-node-8
  • 7488f55 Make binding tests less fragile
  • 10f9a58 Add Node 8 to the support versions lists
  • f2f4b96 Update link for VS 2013 download
  • 7201e98 Update request version to avoid npm warn (#1915)
  • 9905a59 Merge pull request #1885 from xzyfer/fix-rebuild
  • eb7f013 Add binding.js to Coveralls coverage (#1902)
  • f0419a7 Fix npm rebuild

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

Version 1.1.0 of find-root just got published.

Branch Build failing 🚨
Dependency find-root
Current Version 1.0.0
Type dependency

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

find-root is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

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

Version 3.1.0 of eslint-plugin-jsdoc just got published.

Branch Build failing 🚨
Dependency eslint-plugin-jsdoc
Current Version 3.0.2
Type dependency

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

eslint-plugin-jsdoc is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.1.0

<a name"3.1.0">

3.1.0 (2017-05-12)

Features

Commits

The new version differs by 1 commits0.

  • 682b6bd feat: add rule require-example (#35)

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

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

Version 9.1.0 of postcss-import just got published.

Branch Build failing 🚨
Dependency postcss-import
Current Version 9.0.0
Type dependency

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

As postcss-import is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes 9.1.0
  • Added: addModulesDirectories option (#256)
Commits

The new version differs by 2 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 babel-loader is breaking the build 🚨

Version 6.3.0 of babel-loader just got published.

Branch Build failing 🚨
Dependency babel-loader
Current Version 6.2.10
Type dependency

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

As babel-loader is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes v6.3.0

πŸš€ New Feature

Allow to override BABEL_ENV/NODE_ENV at loader-level. Useful for isomorphic applications which have separate babel config for client and server.

πŸ› Bug Fix

  • Update loader-utils dependency to ^0.2.16 to fix compatibility with webpack 2 (#371) @leonaves

πŸ’… Polish

  • Improve FS caching to do less sync calls which improves performance slightly (#375) @akx
Commits

The new version differs by 10 commits .

  • 877e956 6.3.0
  • 4b3bafa FS caching improvements (#375)
  • 0b19a6d Update loader-utils dependecy to ^0.2.16 (#371)
  • 15881f4 Add env query parameter. (#368)
  • e9e3702 Update yarn.lockk
  • 707f31c chore(package): update eslint-config-babel to version 6.0.0 (#360)
  • 5657f48 chore(package): update eslint-config-babel to version 5.0.0 (#359)
  • 757002a Remove plugin-babel (#358)
  • a7e16da Update eslint-config-babel to the latest version πŸš€ (#357)
  • 3900952 Update CHANGELOG.md

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of karma-sauce-launcher is breaking the build 🚨

Version 1.2.0 of karma-sauce-launcher just got published.

Branch Build failing 🚨
Dependency karma-sauce-launcher
Current Version 1.1.0
Type dependency

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

karma-sauce-launcher is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v1.2.0

Features

  • config: add proxy option (bae758a)
  • config: allow SE traffic to be sent via Sauce Connect's Relay (0ac67d4)
  • config: pass parentTunnel to selenium (bae326f)
  • deps: upgrade sauce connect (e792677)
  • launcher: expose commandTimeout, idleTimeout, maxDuration options (3fe1c75), closes #62
Commits

The new version differs by 13 commits.

  • 004d61d chore: release v1.2.0
  • f783f63 chore: update contributors
  • a21fbd9 chore(deps): update dev dependencies
  • 79c70c2 feat(config): expose commandTimeout, idleTimeout, maxDuration options
  • f607303 Merge branch 'master' of https://github.com/JamieMason/karma-sauce-launcher into JamieMason-master
  • 0362ad5 docs(readme): fix SauceLabs doc links
  • 0ac67d4 feat(config): allow SE traffic to be sent via Sauce Connect's Relay
  • 0219065 docs(readme): add hint to platform configurator
  • bae326f feat(config): pass parentTunnel to selenium
  • bae758a feat(config): add proxy option
  • e792677 feat(deps): upgrade sauce connect
  • 79b688c chore(travis): update build config
  • 3fe1c75 feat(launcher): expose commandTimeout, idleTimeout, maxDuration options

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

Version 7.7.1 of stylelint just got published.

Branch Build failing 🚨
Dependency stylelint
Current Version 7.7.0
Type dependency

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

As stylelint is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes 7.7.1
  • Fixed: ensure only absolute filepaths are passed to processors (#2207).
Commits

The new version differs by 8 commits .

  • cb5b48a Prepare 7.7.1
  • 14c81a9 chore(package): update npm-run-all to version 4.0.0 (#2228)
  • 67697f1 package.json: update homepage (#2224)
  • ad1a967 Update CHANGELOG.md
  • e99118e Update CHANGELOG.md
  • e00b3eb Ensure absolute paths to processors (#2207)
  • ebc9e6a Fix typo in docs (#2214)
  • b5145a1 updates to use micromatch (#2201)

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

Version 14.5.0 of browserify was just published.

Branch Build failing 🚨
Dependency browserify
Current Version 14.4.0
Type dependency

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

browserify is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 9 commits.

  • ccc0213 14.5.0
  • f2e720a changelog 14.5.0
  • 37bd7b4 Merge pull request #1733 from dignifiedquire/patch-1
  • 5a0c9ac use ~ range for <v1.0 deps
  • 866a2e7 Merge pull request #1767 from amiller-gh/master
  • 9857f90 Update os-browserify to 0.3.0
  • 0305b70 update readme links and travis badge
  • 9bc05a3 code of conduct
  • 52c0856 bump browserify-zlib to 0.2.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 npm-run-all is breaking the build 🚨

Version 4.1.0 of npm-run-all just got published.

Branch Build failing 🚨
Dependency npm-run-all
Current Version 4.0.2
Type devDependency

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

As npm-run-all is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v4.1.0

Features

  • e07e782 add --aggregate-output option. This option avoids that the output of tasks is mixed even if parallel mode. Don't use this option if a task never finishes (e.g. web server, file watching, ...).
    Thank you, @fatso83 !

Bug fixes

  • f7f7b43 fixed a bug that npm-run-all shows MaxListenersExceededWarning warnings if it runs many tasks in parallel.
Commits

The new version differs by 14 commits.

  • 59219e8 4.1.0
  • f7f7b43 Fix: MaxListenersExceededWarning (fixes #105)
  • 64f6479 Chore: use async/await in tests
  • 66fa8ff Chore: upgrade dependencies
  • 8c8bec0 Docs: update docs
  • 8c6debf Chore: tweak CI settings
  • 5fcc2c6 Chore: no package-lock
  • e07e782 New: add --aggregate-output option (fixes #36)(#104)
  • dff6409 Docs: add note about Yarn compatibility (#103)
  • 94f1b64 Merge pull request #101 from ntwb/patch-1
  • a8364ce Add Node.j 8.x to AppVeyor CI
  • c6d3092 Add Node.js 8.x to Travis CI
  • 873f036 Merge pull request #95 from goto-bus-stop/feature/docs-in-pkg
  • 0fca0e0 Include docs in published npm package.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of karma-firefox-launcher is breaking the build 🚨

Version 1.1.0 of karma-firefox-launcher was just published.

Branch Build failing 🚨
Dependency karma-firefox-launcher
Current Version 1.0.1
Type dependency

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

karma-firefox-launcher 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 8 commits.

  • cf20be3 chore(release): 1.1.0
  • 66812f1 chore: update dev dependencies
  • 98a4ada fix: safe handling of missing env variables
  • fe9d442 Merge pull request #77 from keithamus/patch-2
  • 66cd7ed chore(ci): remove depracted Node versions from Travis.yml
  • ede7023 Merge pull request #79 from mgol/mailmap
  • 5f352c4 chore: add a Git .mailmap with my new name
  • a1fc1c8 feat: support Firefox headless

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

Version 3.5.1 of jsdoc just got published.

Branch Build failing 🚨
Dependency jsdoc
Current Version 3.5.0
Type dependency

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

jsdoc is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes JSDoc 3.5.1

This version of JSDoc includes the following bug fixes:

  • Fixed an issue that prevented JSDoc from working on versions of Node.js prior to 5.10.0.
  • If the JSDoc configuration file does not have a file extension, JSDoc now assumes that the file
    is in JSON format.
Commits

The new version differs by 7 commits ahead by 7, behind by 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 autoprefixer is breaking the build 🚨

Version 6.6.1 of autoprefixer just got published.

Branch Build failing 🚨
Dependency autoprefixer
Current Version 6.6.0
Type dependency

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

As autoprefixer is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes 6.6.1
  • Add metadata to use Autoprefixer in JSS tests (by @cvle).
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 node-sass is breaking the build 🚨

Version 4.6.0 of node-sass was just published.

Branch Build failing 🚨
Dependency node-sass
Current Version 4.5.3
Type dependency

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

node-sass 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 v4.6.0

Fixes

  • Node 9 Support
  • Some Electron ABIs allowed
  • Watcher improvements

Supported Environments

OS Architecture Node
Windows x86 & x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9
OSX x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9
Linux* x86 & x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9
Alpine x64 4, 6, 7, 8
FreeBSD 10+ i386 4, 6, 8
FreeBSD 10+ amd64 4, 6, 8

*Linux support refers to Ubuntu, Debian, and CentOS 5

Commits

The new version differs by 27 commits.

  • 54f9873 4.6.0
  • 0e8ce9c Build: Add Node 9 to Appveyor
  • 82dc901 Install: Add Node 9 detection
  • 8110422 build: Add Node 8 (carbon) to Travis
  • 74242dc Merge pull request #2127 from foladipo/patch-1
  • aa5bbbf improve grammar/clarity of instructions
  • e934a55 Remove Node 0.10 and 0.12 from CI config (#2112)
  • 6ed334b Add workaround for Node < 4 support with v4.x
  • 9e18803 docs: Fix broken anchor for Functions
  • 4a0f3d0 docs: README formatting and spelling fixes (#2063)
  • 5392533 chore: add NPM 5 troubleshooting (#2036)
  • a219c8c Fix broken link to CONTRIBUTING.md
  • 4f9b667 docs: Replace VS 2013 requirement with node-gyp (#2028)
  • 74179fc Fix test exclusion
  • 59fb078 Pass "follow" option to sass-graph

There are 27 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 npm-run is breaking the build 🚨

Version 4.1.2 of npm-run just got published.

Branch Build failing 🚨
Dependency npm-run
Current Version 4.1.1
Type dependency

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

As npm-run is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Commits

The new version differs by 5 commits .

  • 80a842e Release 4.1.2
  • b11bc7d Options is optional.
  • c18c8c5 Options for exec is optional (#13)
  • 7a5127b Update Readme.md
  • 7402040 Drop CI tests for node 4.0 (leave 4.x) test node 7.

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 remark-preset-lint-videojs is breaking the build 🚨

Version 1.0.2 of remark-preset-lint-videojs just got published.

Branch Build failing 🚨
Dependency remark-preset-lint-videojs
Current Version 1.0.1
Type dependency

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

remark-preset-lint-videojs is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 2 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 shelljs is breaking the build 🚨

Version 0.7.8 of shelljs just got published.

Branch Build failing 🚨
Dependency shelljs
Current Version 0.7.7
Type dependency

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

shelljs is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 13 commits.

  • 3864567 0.7.8
  • a66e338 docs(changelog): updated by Nate Fischer [ci skip]
  • bbd8178 Add node 8 to CI (#730)
  • 15558cf fix(mkdir): improve error handling around files (#721)
  • a2e13b6 Properly handle directories as arguments (#713)
  • 951ff22 Add common.buffer (#710)
  • 92d3f39 Fix common.expand error (#709)
  • bbe521b Fix #631 throw error when overwriting recently created file (#702)
  • d8ac4d3 refactor: remove unnecessary common.js imports (#703)
  • 7feabda Remove contents of symlink to dir with rm -rf (#688)
  • e12da9d Refactor: Use process.platform across codebase (#689)
  • 80d590e Small clarification of verbose flag (#691)
  • b9201eb docs(changelog): updated by Nate Fischer [ci skip]

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

Version 4.0.1 of remark-toc just got published.

Branch Build failing 🚨
Dependency remark-toc
Current Version 4.0.0
Type dependency

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

remark-toc is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes 4.0.1
  • a50b91e Add section on related projects
  • 85849cf Refactor example in readme.md
Commits

The new version differs by 13 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 rimraf is breaking the build 🚨

Version 2.6.2 of rimraf just got published.

Branch Build failing 🚨
Dependency rimraf
Current Version 2.6.1
Type dependency

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

rimraf is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 2 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 uuid is breaking the build 🚨

Version 3.1.0 of uuid just got published.

Branch Build failing 🚨
Dependency uuid
Current Version 3.0.1
Type dependency

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

uuid is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 6 commits.

  • c50ac88 Update readme & package version (#198)
  • 082a0b3 v5 support in CLI (#197)
  • 1d56dc9 V5 support (#188)
  • f37f96a (fix) Add .npmignore file to exclude test/ and other non-essential files from packing. (#183)
  • 3b21880 Fix typo (#178)
  • d8e41bd Simple typo fix (#165)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of karma-detect-browsers is breaking the build 🚨

Version 2.2.6 of karma-detect-browsers was just published.

Branch Build failing 🚨
Dependency karma-detect-browsers
Current Version 2.2.5
Type dependency

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

karma-detect-browsers 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 8 commits.

  • 8929455 fix: code style
  • bd37c87 chore: Release v2.2.6
  • 723454a fix: Filter out FirefoxAurora and FirefoxNightly on linux
  • 94c9766 fix: Only launch browser once
  • 52391e5 chore: update node.js versions in travis
  • 9140a0d chore: update dependencies
  • 0da8fa3 Merge pull request #24 from EsrefDurna/master
  • 817292f updated package grunt-contrib-jshint from 1.0.0 to 1.1.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 browserify-banner is breaking the build 🚨

Version 1.0.5 of browserify-banner just got published.

Branch Build failing 🚨
Dependency browserify-banner
Current Version 1.0.4
Type dependency

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

browserify-banner is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 5 commits.

  • 5a044a3 release v1.0.5
  • 0aa30e0 Updated dependencies
  • e2565fd Added a stderr assertion, to get better information about test failure
  • e87b069 npm 5 lockfile
  • 0848a60 added Node 8 to the CI matrix

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

Version 0.3.3 of chg was just published.

Branch Build failing 🚨
Dependency chg
Current Version 0.3.2
Type dependency

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

chg 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 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 karma-teamcity-reporter is breaking the build 🚨

Version 1.0.1 of karma-teamcity-reporter just got published.

Branch Build failing 🚨
Dependency karma-teamcity-reporter
Current Version 1.0.0
Type dependency

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

karma-teamcity-reporter is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v1.0.1

Features

  • add flowId to avoid unstable teamcity output (eef641b)
Commits

The new version differs by 4 commits.

  • f883996 chore: release v1.0.1
  • e7cb5bb chore: update contributors
  • 97cd97d chore: upgrade deps
  • eef641b feat: add flowId to avoid unstable teamcity output

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

Version 2.12.0 of commander was just published.

Branch Build failing 🚨
Dependency commander
Current Version 2.11.0
Type dependency

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

commander 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 v2.12.0
  • add attributeName() method to Option objects
  • Documentation updated for options with --no prefix
  • typings: outputHelp takes a string as the first parameter
  • typings: use overloads
  • feat(typings): update to match js api
  • Print default value in option help
  • Fix translation error
  • Fail when using same command and alias (#491)
  • feat(typings): add help callback
  • fix bug when description is add after command with options (#662)
  • Format js code
  • Rename History.md to CHANGELOG.md (#668)
  • feat(typings): add typings to support TypeScript (#646)
  • use current node
Commits

The new version differs by 15 commits.

  • 7e22f38 version bump 2.12.0
  • 0060dde add attributeName() method to Option objects
  • d359b75 Documentation updated for options with --no prefix
  • 0ae8353 typings: outputHelp takes a string as the first parameter
  • c5511a2 typings: use overloads
  • 7a122e7 feat(typings): update to match js api
  • d9abf56 Print default value in option help
  • b92a7c6 Fix translation error
  • 2f07e29 Fail when using same command and alias (#491)
  • df86179 feat(typings): add help callback
  • 5c74431 fix bug when description is add after command with options (#662)
  • df3b529 Format js code
  • f249c85 Rename History.md to CHANGELOG.md (#668)
  • 66dfb8c feat(typings): add typings to support TypeScript (#646)
  • 90b7fef use current node

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

Version 1.7.1 of karma just got published.

Branch Build failing 🚨
Dependency karma
Current Version 1.7.0
Type dependency

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

karma is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 3 commits.

  • ee40570 chore: release v1.7.1
  • 66b08e6 chore: update contributors
  • ea32194 feat(deps): add support for node@8

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

Version 2.19.0 of browser-sync was just published.

Branch Build failing 🚨
Dependency browser-sync
Current Version 2.18.13
Type dependency

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

browser-sync 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 2 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

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

Version 2.3.3 of qunitjs just got published.

Branch Build failing 🚨
Dependency qunitjs
Current Version 2.3.2
Type dependency

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

qunitjs is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes 2.3.3
  • Core: Updates for Node.js version 8 compatibility and testing
  • Docs: Update README/CONTRIBUTING with more recent/relevant information
  • Docs: Move CONTRIBUTING.md from docs to root
  • Build: Let grunt watch live-reload the test suite
  • Build: Only start one web server for grunt watch
  • Core: Support running in WorkerGlobalScope
  • Docs: Add license status (#1175)
  • Docs: delete note about QUnit.jsDump's removal
  • Docs: Document 'todo' in log details object
  • Docs: Document 'todo' in testDone details object
  • Tests: Add requireQUnit tests
  • CLI: Prefer local version of QUnit
Commits

The new version differs by 15 commits ahead by 15, behind by 1.

  • f34e0d1 2.3.3
  • 7770dec Build: Prepare 2.3.3 release, including authors and history update
  • adb2ba6 Core: Updates for Node.js version 8 compatibility and testing
  • 9c53d97 Docs: Update README/CONTRIBUTING with more recent/relevant information
  • 176f58d Docs: Move CONTRIBUTING.md from docs to root
  • 78b65a0 Build: Let grunt watch live-reload the test suite
  • 95b746b Build: Only start one web server for grunt watch
  • ed8fb54 Core: Support running in WorkerGlobalScope
  • d8fff2f Add license status (#1175)
  • b01669e Docs: delete note about QUnit.jsDump's removal
  • 9177f61 Docs: Document 'todo' in log details object
  • cfc1ebf Docs: Document 'todo' in testDone details object
  • 6d0ef57 Tests: Add requireQUnit tests
  • f6dc7f9 CLI: Prefer local version of QUnit
  • 9e8fb1f Build: Updating the master version to 2.3.3-pre.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of babel-cli is breaking the build 🚨

Version 6.26.0 of babel-cli just got published.

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

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

babel-cli is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

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

Version 3.10.0 of cssnano just got published.

Branch Build failing 🚨
Dependency cssnano
Current Version 3.9.1
Type dependency

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

As cssnano is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes v3.10.0
  • cssnano will no longer console.warn any messages when using deprecated options; these are now sent to PostCSS. You will be able to see them if you use a PostCSS runner with built-in messages support, or alternately by loading postcss-reporter or postcss-browser-reporter in your plugins list.
  • Prepares support for grid identifier reduction by adding it to the list of optimisations turned off when options.safe is set to true.
  • Adds support for normalizing unicode-range descriptors. Values will be converted when the code matches 0 & f in the same place on both sides of the range. So, u+2000-2fff can be converted to u+2???, but u+2100-2fff will be left as it is.
Commits

The new version differs by 15 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 bundle-collapser is breaking the build 🚨

Version 1.3.0 of bundle-collapser just got published.

Branch Build failing 🚨
Dependency bundle-collapser
Current Version 1.2.1
Type dependency

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

bundle-collapser is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 2 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 🌴

CI options

Related to #25 we should support various CI options (Travis/Team City/Circle CI)

An in-range update of remark-man is breaking the build 🚨

Version 5.0.1 of remark-man just got published.

Branch Build failing 🚨
Dependency remark-man
Current Version 5.0.0
Type devDependency

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

As remark-man is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes 5.0.1
Commits

The new version differs by 8 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 babel-loader is breaking the build 🚨

Version 7.1.0 of babel-loader just got published.

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

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

babel-loader is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes 7.1.0

πŸš€ New Feature

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

πŸ› Bug Fix

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

πŸ“ Documentation

  • Remove outdated examples. (Daniel Tschinder)

🏠 Internal

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

The new version differs by 13 commits.

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

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of remark-html is breaking the build 🚨

Version 6.0.1 of remark-html just got published.

Branch Build failing 🚨
Dependency remark-html
Current Version 6.0.0
Type dependency

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

remark-html is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes 6.0.1
Commits

The new version differs by 14 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 mocha.parallel is breaking the build 🚨

Version 0.15.4 of mocha.parallel was just published.

Branch Build failing 🚨
Dependency mocha.parallel
Current Version 0.15.3
Type devDependency

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

mocha.parallel is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 6 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 browser-sync is breaking the build 🚨

Version 2.18.7 of browser-sync just got published.

Branch Build failing 🚨
Dependency browser-sync
Current Version 2.18.6
Type dependency

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

As browser-sync is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Commits

The new version differs by 3 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 remark-slug is breaking the build 🚨

Version 4.2.3 of remark-slug just got published.

Branch Build failing 🚨
Dependency remark-slug
Current Version 4.2.2
Type dependency

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

remark-slug is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes 4.2.3
  • 0dfc244 Add reference to rehype, rehype-slug in readme.md
  • 64d41f3 Update example in readme.md
Commits

The new version differs by 15 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 browserify is breaking the build 🚨

Version 14.3.0 of browserify just got published.

Branch Build failing 🚨
Dependency browserify
Current Version 14.2.0
Type dependency

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

As browserify is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Commits

The new version differs by 4 commits .

  • cd01926 14.3.0
  • 08caf04 changelog
  • ad5060d Merge pull request #1710 from substack/https-browserify-1
  • 7c7b4d4 update https-browserify to ^1.0.0

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

Branch Build failing 🚨
Dependency eslint
Current Version 3.14.1
Type dependency

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

As eslint is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes v3.15.0
  • f2a3580 Fix: no-extra-parens incorrect precedence (fixes #7978) (#7999) (alberto)
  • d6b6ba1 Fix: no-var should fix ForStatement.init (#7993) (Toru Nagashima)
  • 99d386d Upgrade: Espree v3.4.0 (#8019) (Kai Cataldo)
  • 42390fd Docs: update README.md for team (#8016) (Toru Nagashima)
  • d7ffd88 Chore: enable template-tag-spacing on ESLint codebase (#8005) (Teddy Katz)
  • f2be7e3 Docs: Fix typo in object-curly-newline.md (#8002) (Danny Andrews)
  • df2351a Docs: Fix misleading section in brace-style documentation (#7996) (Teddy Katz)
  • 5ae6e00 Chore: avoid unnecessary feature detection for Symbol (#7992) (Teddy Katz)
  • 5d57c57 Chore: fix no-else-return lint error (refs #7986) (#7994) (Vitor Balocco)
  • 62fb054 Chore: enable no-else-return on ESLint codebase (#7986) (Teddy Katz)
  • c59a0ba Update: add ignoreRestSiblings option to no-unused-vars (#7968) (Zack Argyle)
  • 5cdfa99 Chore: enable no-unneeded-ternary on ESLint codebase (#7987) (Teddy Katz)
  • fbd7c13 Update: ensure operator-assignment handles exponentiation operators (#7970) (Teddy Katz)
  • c5066ce Update: add "variables" option to no-use-before-define (fixes #7111) (#7948) (Teddy Katz)
  • 09546a4 New: template-tag-spacing rule (fixes #7631) (#7913) (Jonathan Wilsson)
Commits

The new version differs by 17 commits .

  • 8ea98f9 3.15.0
  • 77b5cb7 Build: package.json and changelog update for 3.15.0
  • f2a3580 Fix: no-extra-parens incorrect precedence (fixes #7978) (#7999)
  • d6b6ba1 Fix: no-var should fix ForStatement.init (#7993)
  • 99d386d Upgrade: Espree v3.4.0 (#8019)
  • 42390fd Docs: update README.md for team (#8016)
  • d7ffd88 Chore: enable template-tag-spacing on ESLint codebase (#8005)
  • f2be7e3 Docs: Fix typo in object-curly-newline.md (#8002)
  • df2351a Docs: Fix misleading section in brace-style documentation (#7996)
  • 5ae6e00 Chore: avoid unnecessary feature detection for Symbol (#7992)
  • 5d57c57 Chore: fix no-else-return lint error (refs #7986) (#7994)
  • 62fb054 Chore: enable no-else-return on ESLint codebase (#7986)
  • c59a0ba Update: add ignoreRestSiblings option to no-unused-vars (#7968)
  • 5cdfa99 Chore: enable no-unneeded-ternary on ESLint codebase (#7987)
  • fbd7c13 Update: ensure operator-assignment handles exponentiation operators (#7970)

There are 17 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

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

Version 7.11.0 of stylelint just got published.

Branch Build failing 🚨
Dependency stylelint
Current Version 7.10.1
Type dependency

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

stylelint is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes 7.11.0
  • Added: experimental autofixing (#2467, #2500, #2529 and #2577). Use --fix CLI parameter or fix: true Node API options property. Supported rules:
    • at-rule-empty-line-before
    • at-rule-name-case
    • color-hex-case
    • comment-empty-line-before
    • custom-property-empty-line-before
    • declaration-empty-line-before
    • indentation
    • rule-empty-line-before
  • Added: selector-max-class rule.
  • Added: ignore: ["custom-elements"] option to selector-type-no-unknown (#2366).
  • Fixed: "Cannot find module 'pify'" regression in node@4 with npm@2 (#2614).
  • Fixed: no error is thrown when linting a string with cache enabled (#2494).
  • Fixed: Less :extend is now ignored (#2571).
  • Fixed: function-parentheses-space-inside now ignores functions without parameters (#2587).
  • Fixed: length-zero-no-unit now correctly handles newlines and no spaces after colon (#2477).
  • Fixed: selector-descendant-combinator-no-non-space and selector-combinator-space-before/after now understand and check >>> shadow-piercing combinator (#2509).
  • Fixed: selector-descendant-combinator-no-non-space now ignores Less guards (#2557).
  • Fixed: selector-pseudo-class-no-unknown now checks @page at-rules and supports @page pseudo-classes (#2445).
  • Fixed: selector-pseudo-class-no-unknown now considers focus-ring, playing and paused to be known (#2507).
  • Fixed: selector-type-no-unknown now ignores MathML tags (#2478).
  • Fixed: selector-type-no-unknown now ignores the /deep/ shadow-piercing combinator (#2508).
  • Fixed: value-keyword-case now ignores variables with signs (#2558).
Commits

The new version differs by 83 commits.

  • 8466d17 Prepare 7.11.0
  • 9cd35c0 Prepare changelog
  • 534c29d Update CHANGELOG.md
  • aee270e Move pify from devDependencies to dependencies
  • e1700b4 fix(package): update known-css-properties to version 0.2.0
  • 7f48674 Update CHANGELOG.md
  • d1c1b13 Add autofixing for color-hex-case (#2577)
  • f0e0780 Create CHANGELOG.md
  • de74769 Add indentation autofixing for selectors, at-rules params, and declarations
  • 79a1ff4 Add docs
  • d09da33 Add indentation autofixing for most usecases
  • 074d9f8 Refactor old code
  • 67b8f50 Update CHANGELOG.md
  • 5796ac4 Fixed: ignore less guards in selector-descendant-combinator-no-non-space. (#2557)
  • b86fc18 Stylelint pre-commit plugin (#2591)

There are 83 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 mocha is breaking the build 🚨

Version 3.5.1 of mocha just got published.

Branch Build failing 🚨
Dependency mocha
Current Version 3.5.0
Type devDependency

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

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

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.5.1

3.5.1 / 2017-09-09

πŸ“° News

  • πŸ“£ Mocha is now sponsoring PDXNode! If you're in the Portland area, come check out the monthly talks and hack nights!

πŸ› Fixes

  • #2997: Fix missing xit export for "require" interface (@solodynamo)
  • #2957: Fix unicode character handling in XUnit reporter failures (@jkrems)

πŸ”© Other

Commits

The new version differs by 14 commits.

  • 4070a44 Release v3.5.1
  • 466ba73 update CHANGELOG.md for v3.5.1 [ci skip]
  • 1cc0fc0 import/require xit, fixes #2972
  • 74fa66f update nyc to latest; remove workaround in travis script
  • aa52933 update coveralls strategy; closes #2984
  • 73a5338 Spelling (#2981)
  • 9f403bf Add utils.escape tests and fix unicode escaping
  • 800acbc whitelist "developer-experience" tag for stalebot [ci skip]
  • 5895671 Added issue, pull request templates. (#2869)
  • 075bd51 Merge pull request #2918 from mochajs/no-shell-test
  • 8710438 Work around Node 0.10 Windows flake when testing
  • 13b8340 Ensure that compiler lookup works and not just that transpilation works (#2922)
  • 26d337a Add tests for double-star behavior
  • c0e6b68 Eliminate glob.sh

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

Version 3.4.0 of mocha just got published.

Branch Build failing 🚨
Dependency mocha
Current Version 3.3.0
Type devDependency

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

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

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.4.0

Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.

This week's highlights:

  • allowUncaught added to commandline as --allow-uncaught (and bugfixed)
  • warning-related Node flags

πŸŽ‰ Enhancements

πŸ› Fixes

πŸ”© Other

Commits

The new version differs by 9 commits0.

  • 7554b31 Add Changelog for v3.4.0
  • 9f7f7ed Add --trace-warnings flag
  • 92561c8 Add --no-warnings flag
  • ceee976 lint test/integration/fixtures/simple-reporter.js
  • dcfc094 Revert "use semistandard directly"
  • 93392dd no special case for macOS running Karma locally
  • 4d1d91d --allow-uncaught cli option
  • fb1e083 fix allowUncaught in browser
  • 4ed3fc5 Add license report and scan status

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

lint-css-css Error: Files glob patterns specified did not match any files

One of our team members has encountered this message in a few cases when trying to lint a new project with CSS/Sass support:

[lint-css-sass      ][info ]: 1 source checked
[lint-css-sass      ][info ]:  src/css/index.scss
[lint-css-sass      ][info ]: 
[lint-css-sass      ][info ]: 0 problems found
[lint-css-sass      ][info ]: 
[lint-css-css       ][info ]: Error: Files glob patterns specified did not match any files
[lint-css-css       ][info ]:     at node_modules/videojs-spellbook/node_modules/stylelint/dist/standalone.js:56:17
[lint-css-css       ][fatal]: command: stylelint, failed with exit code: 80

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.