GithubHelp home page GithubHelp logo

reactor's People

Contributors

designjockey avatar greenkeeper[bot] avatar

Stargazers

avatar

Watchers

avatar avatar

reactor's Issues

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

Version 1.7.0 of eslint-loader just got published.

Branch Build failing 🚨
Dependency eslint-loader
Current Version 1.6.3
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
  • ❌ ci/circleci Your tests failed on CircleCI Details
Release Notes 1.7.0
  • Fixed: outputReport option writes report for last file checked only
    (#160 - @deryni)
  • Added: use babel loader fs cache as the default caching engine
    (#159 - @viankakrisna)
Commits

The new version differs by 5 commits .

  • 966157c 1.7.0
  • 4eae098 Fix failing tests due to webpack minor change
  • 7367f41 Added: use babel loader fs cache as the default caching engine (#159)
  • 1697b94 Fixed: outputReport option writes report for last file checked only (#160)
  • 87cec0d README: Write 'webpack' in lower-case letters (#163)

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

Version 15.5.0 of react-dom just got published.

Branch Build failing 🚨
Dependency react-dom
Current Version 15.4.2
Type dependency

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

As react-dom 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
  • ❌ ci/circleci Your tests failed on CircleCI Details
Release Notes v15.5.0

15.5.0 (April 7, 2017)

React

  • Added a deprecation warning for React.createClass. Points users to create-react-class instead. (@acdlite in d9a4fa4)
  • Added a deprecation warning for React.PropTypes. Points users to prop-types instead. (@acdlite in 043845c)
  • Fixed an issue when using ReactDOM together with ReactDOMServer. (@wacii in #9005)
  • Fixed issue with Closure Compiler. (@anmonteiro in #8895)
  • Another fix for Closure Compiler. (@Shastel in #8882)
  • Added component stack info to invalid element type warning. (@n3tr in #8495)

React DOM

  • Fixed Chrome bug when backspacing in number inputs. (@nhunzaker in #7359)
  • Added react-dom/test-utils, which exports the React Test Utils. (@bvaughn)

React Test Renderer

  • Fixed bug where componentWillUnmount was not called for children. (@gre in #8512)
  • Added react-test-renderer/shallow, which exports the shallow renderer. (@bvaughn)

React Addons

  • Last release for addons; they will no longer be actively maintained.
  • Removed peerDependencies so that addons continue to work indefinitely. (@acdlite and @bvaughn in 8a06cd7 and 67a8db3)
  • Updated to remove references to React.createClass and React.PropTypes (@acdlite in 12a96b9)
  • react-addons-test-utils is deprecated. Use react-dom/test-utils and react-test-renderer/shallow instead. (@bvaughn)
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 webpack-dev-server is breaking the build 🚨

Version 2.9.2 of webpack-dev-server was just published.

Branch Build failing 🚨
Dependency webpack-dev-server
Current Version 2.9.1
Type devDependency

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

webpack-dev-server 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
  • ❌ ci/circleci Your tests failed on CircleCI Details
Release Notes v2.9.2

Bugfixes

Changed property descriptor for Array.includes polyfill (#1134)

Updates

Remove header additional property validation (#1115)
Allow explicitly setting the protocol from the public option (#1117)
Updates readme with support, usage, and caveats (outlines no support for old IE)

Commits

The new version differs by 5 commits.

  • 32412bb 2.9.2
  • 1af8f0e Remove header property validation (#1115)
  • c490b24 allow explicitly setting the protocol from the public option (#1117)
  • ee7231b Changed property descriptor for Array.includes polyfill (#1134)
  • 5a7f26b updating readme with support, usage, and caveats

See the full diff

FAQ and help

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

Your Greenkeeper Bot 🌴

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

Version 2.9.2 of eslint-plugin-jasmine was just published.

Branch Build failing 🚨
Dependency eslint-plugin-jasmine
Current Version 2.9.1
Type devDependency

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

eslint-plugin-jasmine 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
  • ❌ ci/circleci Your tests failed on CircleCI Details
Commits

The new version differs by 2 commits.

  • 31e897a fix(docs): adding the lint rule names to the title
  • a05151f fix(docs): add rule name to the title

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

Version 15.5.2 of react-dom just got published.

Branch Build failing 🚨
Dependency react-dom
Current Version 15.5.1
Type dependency

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

As react-dom 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
  • ❌ ci/circleci Your tests failed on CircleCI 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 react-dom is breaking the build 🚨

Version 15.5.3 of react-dom just got published.

Branch Build failing 🚨
Dependency react-dom
Current Version 15.5.2
Type dependency

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

As react-dom 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
  • ❌ ci/circleci Your tests failed on CircleCI 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 webpack is breaking the build 🚨

Version 2.5.0 of webpack just got published.

Branch Build failing 🚨
Dependency webpack
Current Version 2.4.1
Type devDependency

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

As webpack 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 - ❌ **ci/circleci** Your tests failed on CircleCI [Details](https://circleci.com/gh/designjockey/reactor/65?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Release Notes v2.5.0

Bugfixes:

  • add hashSalt to schema
  • webpack's source code no longer contains sourceMappingURL, which caused issues with some tools
  • Added missing semicolon in dll-imported modules
  • DllPlugin manifest is smaller (not pretty printed)
  • CommonsChunkPlugin in async mode doesn't extract from initial chunks

Features:

  • allow placeholders in the BannerPlugin
  • add option to disable the module trace in stats
Commits

The new version differs by 81 commits0.

  • bf3652b 2.5.0
  • cd1cd29 Merge pull request #4815 from webpack/bugfix/extract-async-initial
  • b45588b CommonsChunkPlugin in async mode doesn't select initial chunks
  • 8bab88c Merge pull request #4814 from webpack/test/move-entry
  • a244879 add testcase for moving entry modules into the commons chunk
  • 85dc98f Merge pull request #4813 from JLHwung/perf/date-now
  • 6afc397 perf: use Date.now() instead of new Date().getTime()
  • 94d0641 perf: use Date.now() instead of +new Date()
  • c91ba49 Merge pull request #4791 from deificx/master
  • 94ba75f Merge pull request #4794 from ndresx/disable-manifest-json-pretty-print
  • 84ea1ff added error to stats.moduleTrace test name to trigger test cases corretly
  • 8ad4386 test cases for stats.moduleTrace option
  • 958156a moduleTrace added to webpackOptionsSchema.json
  • de87f93 Disable manifest.json pretty print
  • 4131013 rename stats.stackTrace to stats.moduleTrace

There are 81 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 react-dom is breaking the build 🚨

Version 15.5.1 of react-dom just got published.

Branch Build failing 🚨
Dependency react-dom
Current Version 15.5.0
Type dependency

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

As react-dom 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
  • ❌ ci/circleci Your tests failed on CircleCI 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 karma-webpack is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.0.10 of karma-webpack was just published.

Branch Build failing 🚨
Dependency karma-webpack
Current Version 2.0.9
Type devDependency

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

karma-webpack 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
  • ❌ ci/circleci Your tests failed on CircleCI Details
FAQ and help

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

Your Greenkeeper Bot 🌴

Modules cleanup

Remove "babel-plugin-transform-runtime": "^6.9.0", and "babel-runtime": "^6.9.2", because these do not need to be there with babel-polyfill and remove transform runtime plugin from babelrc.

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

Version 6.25.0 of babel-core just got published.

Branch Build failing 🚨
Dependency babel-core
Current Version 6.24.1
Type devDependency

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

As babel-core 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
  • ❌ ci/circleci Your tests failed on CircleCI 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 🌴

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.