chrishelgert / react-handler Goto Github PK
View Code? Open in Web Editor NEWA react-component for handling typical react/redux-states
License: MIT License
react-handler's People
Contributors
![greenkeeper[bot] avatar](https://avatars.githubusercontent.com/in/505?v=4 "greenkeeper[bot]")
Stargazers
Watchers
react-handler's Issues
An in-range update of babel-core is breaking the build 🚨
Version 6.22.1 of babel-core just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | babel-core |
| Current Version | 6.22.0 |
| 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
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.
engineswas only updated if it defined a single version, not a range..nvmrcwas updated to Node.js 10.travis.ymlwas only changed if there was a root-levelnode_jsthat didn’t already include Node.js 10, such asnodeorlts/*. 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 babel-loader is breaking the build 🚨
Version 6.4.1 of babel-loader just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | babel-loader |
| Current Version | 6.4.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As babel-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
Release Notes
v6.4.1🐛 Bug Fix
- Fixed reset of BABEL_ENV when options.forceEnv is used (#420) @nikopavlica
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 cross-env is breaking the build 🚨
Version 3.2.0 of cross-env just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | cross-env |
| Current Version | 3.1.4 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As cross-env 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
Release Notes
v3.2.0<a name"3.2.0">
3.2.0 (2017-03-04)
Features
Commits
The new version differs by 4 commits .
dad00c4feat(revamp): revamp the entire lib (backward compatible) (#63)e33a85cdocs(README): Add doc for cross-var. (#58)5e590ecdocs(README): added how to use cross-env to run npm sub-scripts (#53)afdb2dedocs(README): mention Bash on Windows (#49)
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.22.1 of babel-cli just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | babel-cli |
| Current Version | 6.22.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As babel-cli 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
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 standard is breaking the build 🚨
Version 10.0.1 of standard just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | standard |
| Current Version | 10.0.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As standard 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
Commits
The new version differs by 12 commits .
d37028eauthors6b48c9f10.0.1332e0ffchangelog9f63f6beslint-plugin-standard@~3.0.11b08ba2[email protected]9cb1097[email protected]4c888b0Merge pull request #839 from feross/watson-patch-18fd2b37Update README.md59e8048Add the word IRC to README.mdf107095changelog9223ed2changelogce20f3cchangelog
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 is breaking the build 🚨
There have been updates to the react monorepo:
-
- The
devDependencyreact was updated from16.6.1to16.6.2.
- The
- The
devDependencyreact-test-renderer was updated from16.6.1to16.6.2.
This version is covered by your current version range and after updating it in your project the build failed.
This monorepo update includes releases of one or more dependencies which all belong to the react group definition.
react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
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-preset-es2015 is breaking the build 🚨
Version 6.22.0 of babel-preset-es2015 just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | babel-preset-es2015 |
| Current Version | 6.18.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As babel-preset-es2015 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
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
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.