Latest version of react gives PropTypes warning

[BrockWills]

With React 15.5, importing PropTypes from React is deprecated in favour of importing from the new 'prop-types' package.

See this link: https://facebook.github.io/react/blog/2017/04/07/react-v15.5.0.html

Thus, using react-toolbox with the latest version of react gives a deprecation warning in the console.

Will look into a PR for this.

[vldmr1986]

The same warnings:

• in my local console:
  warning "react-toolbox@2.0.0-beta.6" has incorrect peer dependency "react@^0.14 || ~15.4.0".
  warning "react-toolbox@2.0.0-beta.6" has incorrect peer dependency "react-dom@^0.14.0 || ~15.4.0".
• browser console:
  Warning: Accessing PropTypes via the main React package is deprecated. Use the prop-types package from npm instead.

[flexzero]

+1

[BrockWills]

#1413 Should hopefully solve this

[mytechnotalent]

Utilizing the FlipMove package causes the PropTypes deprecated warning even after following the best practice illustrated here: https://facebook.github.io/react/blog/2017/04/07/react-v15.5.0.html

[sjain-mi9]

Even after importing PropTypes from prop-types, I'm receiving the same Warning.
"react-toolbox": "^2.0.0-beta.8"
"prop-types": "15.5.8"
"react": "^15.5.4"

[Lrigh1]

Same here! Importing react-flip-move gives me the error, despite having the correct and updated proptypes import.

[marceloaugustocwb]

Also with me:

"dependencies": {
    "classnames": "^2.2.5",
    "firebase": "^3.7.5",
    "firebaseui": "^1.0.1",
    "immutability-helper": "^2.1.2",
    "lodash": "^4.17.4",
    "re-base": "^2.7.0",
    "react": "^15.5.4",
    "react-dom": "^15.5.4",
    "react-router-dom": "^4.1.1",
    "react-tag-input": "^4.7.1",
    "reactfire": "^1.0.0",
    "slugify": "^1.1.0"
  },

[BrunoQuaresma]

+1

[Kliton]

+1

[raunofreiberg]

Getting the same error here.

[Omortis]

Same here. Note that I'm not using PropTypes directly anywhere in my code though it seems to be called out many times by imported modules.

react@15.5.4
prop-types@15.5.10

Looks like it's mostly bootstrap 0.30 doing the dirty work?

[oshalygin]

Same issue, not using PropTypes from the react package anywhere in my code but its still throwing this warning.

EDIT: If anyone is still having my issue, make sure its not another package. A simple way is to pull up the dev tools and then look through the warning stacktrace by putting a breakpoint on the error and refreshing the page. Go up the callstack.