Code Monkey home page Code Monkey logo

webpack-cluster's Introduction

NPM version Travis build status AppVeyor build status Code Climate GPA Code Climate Coverage Dependency Status Development Dependency Status Greenkeeper badge

webpack-cluster

Helps to make parallel webpack compilation easily

Installation

npm install webpack-cluster --save-dev

or

yarn add webpack-cluster --dev

Usage

CLI

$ webpack-cluster --config=**/webpack.config.js [options]

Options:
  --config       Specifies configuration files using `glob` pattern
                                                              [array] [required]
  --failures     Sets failure options                            [default: true]
  --watch        Enables `watch` mode                                  [boolean]
  --dryRun       Enables `dryRun` mode                                 [boolean]
  --concurrency  Sets maximum number of concurrent compilers
                                                           [number] [default: 8]
  --silent       Suppress all output                                   [boolean]

Miscellaneous:
  --version  Outputs version number                                    [boolean]

Node API

import WebpackCluster from 'webpack-cluster';

const webpackCluster = new WebpackCluster({
    dryRun: false,
    concurrency: 10,
    failures: {
        sysErrors: true,
        errors: true,
        warnings: true
    }
});

webpackCluster.run([
    './src/**/webpack.config.js'
]).then(results => { // In case of success
    console.log(results); // ['./src/app1/webpack.config.js', './src/app2/webpack.config.js']
}).catch(results => { // In case of any errors
    console.log(results); // [Error { filename: './src/app3/webpack.config.js', code: 2 }]
});

./gulpfile.js

import gulp from 'gulp';
import gutil from 'gulp-util';
import WebpackCluster from 'webpack-cluster';

const webpackCluster = new WebpackCluster({
    dryRun: false,
    concurrency: 10,
    failures: {
        sysErrors: true,
        errors: true,
        warnings: true
    }
});

gulp.task('run', [], callback => {
    webpackCluster.run([
        './src/**/webpack.config.js'
    ]).then(callback).catch(err => {
        callback(new gutil.PluginError('webpack-cluster', err));
    });
});

gulp.task('watch', [], callback => {
    webpackCluster.watch([
        './src/**/webpack.config.js'
    ]).then(callback).catch(err => {
        callback(new gutil.PluginError('webpack-cluster', err));
    });
});

webpack-cluster's People

Contributors

greenkeeper[bot] avatar greenkeeperio-bot avatar mdreizin avatar

Stargazers

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

Watchers

 avatar  avatar

webpack-cluster's Issues

Allowing arrays as exports from webpack-config

Webpack allows the export of its config file to be an array. This is very helpful, for example when you create configurations programmatically from a list of browsers. However webpack-cluster does not support this.

Let me know what you think about adding this feature.

Consider PR into Webpack core.

It looks like you are using a lot of the core libs to perform some of this parallel functionality. Would you consider submitting a PR to webpack/webpack

If it speeds up any webpack build out of the box with out a doubt it would be great to integrate it to core like we've done with other plugins.

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

Version 2.1.0 of fs-extra just got published.

Branch Build failing ๐Ÿšจ
Dependency fs-extra
Current Version 2.0.0
Type devDependency

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

As fs-extra is โ€œonlyโ€ a devDependency of this project it might not break production or downstream projects, but โ€œonlyโ€ your build or test tools โ€“ preventing new deploys or publishes.

I recommend you give this issue a high priority. Iโ€™m sure you can resolve this ๐Ÿ’ช


Status Details
  • โŒ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details

  • โŒ dependency-ci An error occured Details

  • โŒ continuous-integration/travis-ci/push The Travis CI build is in progress Details

Commits

The new version differs by 87 commits .

  • 90b3609 2.1.0
  • 6ebcb9c Update CHANGELOG
  • efe0d80 Merge pull request #378 from jdalton/move-check
  • 8d978db Don't move when source and dest paths are the same.
  • cf2c50d Merge pull request #386 from jprichardson/changelog
  • 4db96c5 Update CHANGELOG
  • 1f30161 Merge pull request #384 from jprichardson/docs-cleanup-async-methods
  • 83a6190 docs: Refactor remove exmaple to use remove instead of removeSync
  • 936011e docs: Refactor remove and removeSync parameter name
  • fc5fca9 docs: Refactor docs to include parameters type
  • e46b820 Merge pull request #383 from jprichardson/docs-refactor-readJson-example
  • a4f6481 docs/readJson.md: Refactor example for readJson method, refactor move and moveSync tests descriptions
  • b5c72dc Merge pull request #382 from jprichardson/docs-split-out-sync-methods
  • 10756de docs: Refactor readJsonSync example
  • 02c2a62 Docs: Split out sync methods

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

Not sure how things should work exactly?

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


Your Greenkeeper Bot ๐ŸŒด

An in-range update of babel-plugin-transform-builtin-extend is breaking the build ๐Ÿšจ

Version 1.1.1 of babel-plugin-transform-builtin-extend just got published.

Branch Build failing ๐Ÿšจ
Dependency babel-plugin-transform-builtin-extend
Current Version 1.1.0
Type devDependency

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

As babel-plugin-transform-builtin-extend 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
  • โœ… dependency-ci Dependencies checked Details

  • โœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details

  • โŒ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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 eslint-loader is breaking the build ๐Ÿšจ

Version 1.6.3 of eslint-loader just got published.

Branch Build failing ๐Ÿšจ
Dependency eslint-loader
Current Version 1.6.2
Type devDependency

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

As eslint-loader is โ€œonlyโ€ a devDependency of this project it might not break production or downstream projects, but โ€œonlyโ€ your build or test tools โ€“ preventing new deploys or publishes.

I recommend you give this issue a high priority. Iโ€™m sure you can resolve this ๐Ÿ’ช


Status Details
  • โŒ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details

  • โŒ dependency-ci An error occured Details

Release Notes 1.6.3
  • Fixed: ignore cache when eslint rules have changed (#151 - @wrakky)
Commits

The new version differs by 2 commits .

  • d7f003d 1.6.3
  • c667541 Fixed: ignore cache when eslint rules have changed (#151)

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

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

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

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

As eslint-plugin-babel 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
  • โœ… dependency-ci Dependencies checked Details

  • โœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details

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

Release Notes v4.1.0

New

  • babel/semi: Includes class properties (๐Ÿ›  ) #121

Thanks to @aaronjensen

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 ๐ŸŒด

watch example please?

I'm migrating over from your example in webpack-config-stream and I can't figure out how to setup a gulp task to watch

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

Version 3.5.0 of jsdoc just got published.

Branch Build failing ๐Ÿšจ
Dependency jsdoc
Current Version 3.4.3
Type devDependency

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

As jsdoc 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
  • โœ… dependency-ci Dependencies checked Details
  • โœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details
  • โŒ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes JSDoc 3.5.0

This version of JSDoc includes the following major changes:

  • JSDoc now uses the Babylon JavaScript parser, which means that
    JSDoc can parse any JavaScript or JSX file that is supported by the Babel
    compiler.
  • You can now use a JavaScript file to configure JSDoc. See the
    documentation for details and examples.
  • Fixed multiple issues with documenting ES2015 classes and modules.
  • JSDoc now requires Node.js 4.2.0 or later.

For a complete list of changes, see the changelog on GitHub.

Commits

The new version differs by 112 commits ahead by 112, behind by 45.

  • cdd00c0 3.5.0
  • 50d6119 update 3.5.0 changelog
  • e94a598 3.5.0 changelog
  • 5d0b690 reformat changelog
  • c50a4c0 add yields tag (#1388)
  • f31a011 resolve the path to the JS config file before requiring it (#1386)
  • d95cbdd support namespaces that are also functions (#955)
  • 9f8853a add hideconstructor tag (#952)
  • ca1c4f2 add package tag (#962)
  • 6275e69 autodetect default and repeatable parameters when a function is assigned to a variable (#1054)
  • 0e4f1a9 correctly document constructors and instance properties of ES2015 classes (#1182)
  • 67db938 add sourceType config option
  • f101798 fix crash when the author tag is empty (#1289)
  • 43a117d add recurseDepth config option (#1340)
  • 8f5c60b support bigint

There are 112 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 jsdoc is breaking the build ๐Ÿšจ

The devDependency jsdoc was updated from 3.5.5 to 3.6.0.

๐Ÿšจ View failing branch.

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

jsdoc 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 105 commits ahead by 105, behind by 58.

  • 2099e72 3.6.0
  • d45c5b8 Add 3.6.0 changelog.
  • b8012f4 Update dependencies, plus the URLs for the GitHub repos and docs.
  • 10c004f update docs with new template (#1604)
  • aa0b6c1 switch to new-ish ECMAScript syntax
  • 1546d40 update ESLint config
  • 27f9a33 migrate from babylon to @babel/parser
  • d310908 Update ajv to the latest version ๐Ÿš€ (#1599)
  • ccb70aa only run CI with Node.js versions that actually exist
  • 2d3b55b migrate from markdown-it-named-headers to markdown-it-anchor (#1481)
  • 7b304d8 update dependencies and supported Node.js versions
  • b214273 3.5.5 changelog
  • 932c357 Prefer copyFileSync from here over native (#1440)
  • 8e2f868 upgrade Babylon
  • 96f8875 fix test breakage

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

Version 7.2.1 of babel-eslint just got published.

Branch Build failing ๐Ÿšจ
Dependency babel-eslint
Current Version 7.2.0
Type devDependency

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

As babel-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
  • โœ… dependency-ci Dependencies checked Details

  • โœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details

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

Commits

The new version differs by 6 commits .

  • 3cda62e 7.2.1
  • 5626de1 Remove left over eslint 2 estraverse code (#452)
  • b5fb53b Fix type param and interface declaration scoping (#449)
  • f1cee0f Remove lodash dependency (#450)
  • eb05812 Format non-regression errors for legibility (#451)
  • 7972a05 Update README.md with codeFrame option (#448)

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

Version 0.4.1 of codeclimate-test-reporter just got published.

Branch Build failing ๐Ÿšจ
Dependency codeclimate-test-reporter
Current Version 0.4.0
Type devDependency

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

As codeclimate-test-reporter 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
  • โœ… dependency-ci Dependencies checked Details

  • โœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details

  • โŒ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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 ๐ŸŒด

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! ๐ŸŽŠ

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml

If youโ€™re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didnโ€™t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didnโ€™t touch job or matrix configurations because these tend to be quite specific and complex, and itโ€™s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what youโ€™re doing it may require additional work or may not be applicable at all. Weโ€™re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, Iโ€™m a humble robot and wonโ€™t feel rejected ๐Ÿค–


FAQ and help

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


Your Greenkeeper Bot ๐ŸŒด

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

Version 3.16.0 of eslint just got published.

Branch Build failing ๐Ÿšจ
Dependency eslint
Current Version 3.15.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
  • โœ… dependency-ci Dependencies checked Details

  • โœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details

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

Release Notes v3.16.0
  • d89d0b4 Update: fix quotes false negative for string literals as template tags (#8107) (Teddy Katz)
  • 21be366 Chore: Ensuring eslint:recommended rules are sorted. (#8106) (Kevin Partington)
  • 360dbe4 Update: Improve error message when extend config missing (fixes #6115) (#8100) (alberto)
  • f62a724 Chore: use updated token iterator methods (#8103) (Kai Cataldo)
  • daf6f26 Fix: check output in RuleTester when errors is a number (fixes #7640) (#8097) (alberto)
  • cfb65c5 Update: make no-lone-blocks report blocks in switch cases (fixes #8047) (#8062) (Teddy Katz)
  • 290fb1f Update: Add includeComments to getTokenByRangeStart (fixes #8068) (#8069) (Kai Cataldo)
  • ff066dc Chore: Incorrect source code test text (#8096) (Jack Ford)
  • 14d146d Docs: Clarify --ext only works with directories (fixes #7939) (#8095) (alberto)
  • 013a454 Docs: Add TSC meeting quorum requirement (#8086) (Kevin Partington)
  • 7516303 Fix: sourceCode.getTokenAfter shouldn't skip tokens after comments (#8055) (Toru Nagashima)
  • c53e034 Fix: unicode-bom fixer insert BOM in appropriate location (fixes #8083) (#8084) (pantosha)
  • 55ac302 Chore: fix the timing to define rules for tests (#8082) (Toru Nagashima)
  • c7e64f3 Upgrade: mock-fs (#8070) (Toru Nagashima)
  • acc3301 Update: handle uncommon linebreaks consistently in rules (fixes #7949) (#8049) (Teddy Katz)
  • 591b74a Chore: enable operator-linebreak on ESLint codebase (#8064) (Teddy Katz)
  • 6445d2a Docs: Add documentation for /* exported */ (fixes #7998) (#8065) (Lee Yi Min)
  • fcc38db Chore: simplify and improve performance for autofix (#8035) (Toru Nagashima)
  • b04fde7 Chore: improve performance of SourceCode constructor (#8054) (Teddy Katz)
  • 90fd555 Update: improve null detection in eqeqeq for ES6 regexes (fixes #8020) (#8042) (Teddy Katz)
  • 16248e2 Fix: no-extra-boolean-cast incorrect Boolean() autofixing (fixes #7977) (#8037) (Jonathan Wilsson)
  • 834f45d Update: rewrite TokenStore (fixes #7810) (#7936) (Toru Nagashima)
  • 329dcdc Chore: unify checks for statement list parents (#8048) (Teddy Katz)
  • c596690 Docs: Clarify generator-star-spacing config example (fixes #8027) (#8034) (Hรฒa Trแบงn)
  • a11d4a6 Docs: fix a typo in shareable configs documentation (#8036) (Dan Homola)
  • 1e3d4c6 Update: add fixer for no-unused-labels (#7841) (Teddy Katz)
  • f47fb98 Update: ensure semi-spacing checks import/export declarations (#8033) (Teddy Katz)
  • e228d56 Update: no-undefined handles properties/classes/modules (fixes #7964) (#7966) (Kevin Partington)
  • 7bc92d9 Chore: fix invalid test cases (#8030) (Toru Nagashima)
Commits

The new version differs by 31 commits .

  • 3c26a59 3.16.0
  • 5bdb960 Build: package.json and changelog update for 3.16.0
  • d89d0b4 Update: fix quotes false negative for string literals as template tags (#8107)
  • 21be366 Chore: Ensuring eslint:recommended rules are sorted. (#8106)
  • 360dbe4 Update: Improve error message when extend config missing (fixes #6115) (#8100)
  • f62a724 Chore: use updated token iterator methods (#8103)
  • daf6f26 Fix: check output in RuleTester when errors is a number (fixes #7640) (#8097)
  • cfb65c5 Update: make no-lone-blocks report blocks in switch cases (fixes #8047) (#8062)
  • 290fb1f Update: Add includeComments to getTokenByRangeStart (fixes #8068) (#8069)
  • ff066dc Chore: Incorrect source code test text (#8096)
  • 14d146d Docs: Clarify --ext only works with directories (fixes #7939) (#8095)
  • 013a454 Docs: Add TSC meeting quorum requirement (#8086)
  • 7516303 Fix: sourceCode.getTokenAfter shouldn't skip tokens after comments (#8055)
  • c53e034 Fix: unicode-bom fixer insert BOM in appropriate location (fixes #8083) (#8084)
  • 55ac302 Chore: fix the timing to define rules for tests (#8082)

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

Version 1.0.0-beta.6 of eslint-plugin-markdown just got published.

Branch Build failing ๐Ÿšจ
Dependency eslint-plugin-markdown
Current Version 1.0.0-beta.4
Type devDependency

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

As eslint-plugin-markdown is โ€œonlyโ€ a devDependency of this project it might not break production or downstream projects, but โ€œonlyโ€ your build or test tools โ€“ preventing new deploys or publishes.

I recommend you give this issue a high priority. Iโ€™m sure you can resolve this ๐Ÿ’ช

Status Details - โŒ **continuous-integration/appveyor/branch** Waiting for AppVeyor build to complete [Details](https://ci.appveyor.com/project/mdreizin/webpack-cluster/build/95),- โœ… **dependency-ci** Dependencies checked [Details](https://dependencyci.com/builds/202861),- โŒ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/Fitbit/webpack-cluster/builds/227264287?utm_source=github_status&utm_medium=notification)

Release Notes v1.0.0-beta.6
  • c5e9d67 Build: Explicitly specify package.json files (#67) (Brandon Mills)
Commits

The new version differs by 10 commits0.

  • 65e296d 1.0.0-beta.6
  • 07d179f Build: changelog update for 1.0.0-beta.6
  • c5e9d67 Build: Explicitly specify package.json files (#67)
  • 8d5ae99 1.0.0-beta.5
  • 91b3fa9 Build: changelog update for 1.0.0-beta.5
  • 7bd0f6e Build: Install eslint-release (#66)
  • 48122eb Build: Dogfood plugin without npm link (#65)
  • cc7deea Chore: Increase code coverage (#64)
  • 29f2f05 Build: Use eslint-release (#63)
  • d2f2962 Upgrade: remark (#62)

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

Version 10.3.2 of nyc just got published.

Branch Build failing ๐Ÿšจ
Dependency nyc
Current Version 10.3.1
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
  • โœ… dependency-ci Dependencies checked Details,- โŒ continuous-integration/travis-ci/push The Travis CI build failed Details,- โœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details

Commits

The new version differs by 2 commits0.

  • e062a86 chore(release): 10.3.2
  • 213206f fix: we should not create a cache folder if cache is false (#567)

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

Version 6.25.0 of babel-runtime just got published.

Branch Build failing ๐Ÿšจ
Dependency babel-runtime
Current Version 6.23.0
Type dependency

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

babel-runtime 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
  • โœ… dependency-ci Dependencies checked Details
  • โœ… continuous-integration/appveyor/branch AppVeyor build succeeded 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 jasmine is breaking the build ๐Ÿšจ

Version 2.6.0 of jasmine just got published.

Branch Build failing ๐Ÿšจ
Dependency jasmine
Current Version 2.5.3
Type devDependency

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

As jasmine 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 - โœ… **dependency-ci** Dependencies checked [Details](https://dependencyci.com/builds/199090),- โœ… **continuous-integration/appveyor/branch** AppVeyor build succeeded [Details](https://ci.appveyor.com/project/mdreizin/webpack-cluster/build/89),- โŒ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/Fitbit/webpack-cluster/builds/225377289)

Release Notes 2.6.0

Please see the release notes

Commits

The new version differs by 9 commits0.

  • 94de6d5 Bump version to 2.6.0
  • 6c3656f Merge branch 'lonelyelk-expose-reporters-management-api'
  • 6cb6d27 Making jshint pass.
  • 6f44d31 Expose closeReporters methos in the wrapper
  • 023455c Try to detect a exit being called inside the suite
  • 80e6b33 Merge branch 'add-config-option' of https://github.com/bcaudan/jasmine-npm into bcaudan-add-config-option
  • 77acbb1 Merge branch 'bcaudan-reject-unknown-options'
  • 88b838b Fix #53 - Reject unknown options
  • f527ab8 Fix #85 - Option to specify path to your jasmine.json

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

The devDependency eslint-plugin-markdown was updated from 1.0.0-beta.8 to 1.0.0-rc.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-markdown is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • โŒ continuous-integration/appveyor/branch: Waiting for AppVeyor build to complete (Details).
  • โŒ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v1.0.0-rc.0
  • 8fe9a0e New: Enable autofix with --fix (fixes #58) (#97) (Bohdan Khodakivskyi)
  • a5d0cce Fix: Ignore anything after space in code fence's language (fixes #98) (#99) (Francisco Ryan Tolmasky I)
  • 6fd340d Upgrade: [email protected] (#100) (Teddy Katz)
  • dff8e9c Fix: Emit correct endLine numbers (#88) (Paul Murray)
  • 83f00d0 Docs: Suggest disabling strict in .md files (fixes #94) (#95) (Brandon Mills)
  • 3b4ff95 Build: Test against Node v10 (#96) (Brandon Mills)
  • 6777977 Breaking: required node version 6+ (#89) (่–›ๅฎš่ฐ”็š„็Œซ)
  • 5582fce Docs: Updating CLA link (#93) (Pablo Nevares)
  • 24070e6 Build: Upgrade to [email protected] (#92) (Brandon Mills)
  • 6cfd1f0 Docs: Add unicode-bom to list of unsatisfiable rules (#91) (Brandon Mills)
Commits

The new version differs by 12 commits.

  • f9258b7 1.0.0-rc.0
  • 8bc7c0c Build: changelog update for 1.0.0-rc.0
  • 8fe9a0e New: Enable autofix with --fix (fixes #58) (#97)
  • a5d0cce Fix: Ignore anything after space in code fence's language (fixes #98) (#99)
  • 6fd340d Upgrade: [email protected] (#100)
  • dff8e9c Fix: Emit correct endLine numbers (#88)
  • 83f00d0 Docs: Suggest disabling strict in .md files (fixes #94) (#95)
  • 3b4ff95 Build: Test against Node v10 (#96)
  • 6777977 Breaking: required node version 6+ (#89)
  • 5582fce Docs: Updating CLA link (#93)
  • 24070e6 Build: Upgrade to [email protected] (#92)
  • 6cfd1f0 Docs: Add unicode-bom to list of unsatisfiable rules (#91)

See the full diff

FAQ and help

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


Your Greenkeeper Bot ๐ŸŒด

Recommend Projects

  • React photo React

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

  • Vue.js photo Vue.js

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

  • Typescript photo Typescript

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

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

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

Recommend Topics

  • javascript

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

  • web

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

  • server

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

  • Machine learning

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

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

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

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.