Where can I find out where the react proptypes warning is coming from?
I recently bumped our react version to 15.6.2, which includes the React PropTypes deprecation warning. I ran the JSCodeshift codemod script in our project directory and it successfully modified hundreds of files. However, in our webpack for npm run build, I still get this: Warning: Accessing PropTypes via the main React package is deprecated, and will be removed in React v16.0. Use the latest available v15.* prop-types package from npm instead. For info on usage, compatibility, migration and more..... Where and how can I track down the file(s) that are causing this warning message to output? It is not showing up in the developer console, just in my terminal.
reactjs react-proptypes
asked Jun 28 '18 at 22:04
JustinJustin
3517
add a comment |
I recently bumped our react version to 15.6.2, which includes the React PropTypes deprecation warning. I ran the JSCodeshift codemod script in our project directory and it successfully modified hundreds of files. However, in our webpack for npm run build, I still get this: Warning: Accessing PropTypes via the main React package is deprecated, and will be removed in React v16.0. Use the latest available v15.* prop-types package from npm instead. For info on usage, compatibility, migration and more..... Where and how can I track down the file(s) that are causing this warning message to output? It is not showing up in the developer console, just in my terminal.
reactjs react-proptypes
asked Jun 28 '18 at 22:04
JustinJustin
3517
A naive project-wide search forReact.PropTypesmight just work?
– Tholle
Jun 28 '18 at 22:10
1
Tried that with IntelliJ, no results. Which is why I'm confused I keep getting that warning, and would be helpful if I could find exactly which file is throwing it
– Justin
Jun 28 '18 at 22:26
I am experiencing the same issue. I assume this is from a dependency, but I'm at a loss to determine which one.
– Zach
Jan 3 at 1:52
add a comment |
I recently bumped our react version to 15.6.2, which includes the React PropTypes deprecation warning. I ran the JSCodeshift codemod script in our project directory and it successfully modified hundreds of files. However, in our webpack for npm run build, I still get this: Warning: Accessing PropTypes via the main React package is deprecated, and will be removed in React v16.0. Use the latest available v15.* prop-types package from npm instead. For info on usage, compatibility, migration and more..... Where and how can I track down the file(s) that are causing this warning message to output? It is not showing up in the developer console, just in my terminal.
reactjs react-proptypes
asked Jun 28 '18 at 22:04
JustinJustin
3517
I recently bumped our react version to 15.6.2, which includes the React PropTypes deprecation warning. I ran the JSCodeshift codemod script in our project directory and it successfully modified hundreds of files. However, in our webpack for npm run build, I still get this: Warning: Accessing PropTypes via the main React package is deprecated, and will be removed in React v16.0. Use the latest available v15.* prop-types package from npm instead. For info on usage, compatibility, migration and more..... Where and how can I track down the file(s) that are causing this warning message to output? It is not showing up in the developer console, just in my terminal.
reactjs react-proptypes
reactjs react-proptypes
asked Jun 28 '18 at 22:04
JustinJustin
3517
asked Jun 28 '18 at 22:04
JustinJustin
3517
asked Jun 28 '18 at 22:04
JustinJustin
3517
asked Jun 28 '18 at 22:04
JustinJustin
3517
asked Jun 28 '18 at 22:04
JustinJustin
3517
3517
A naive project-wide search forReact.PropTypesmight just work?
– Tholle
Jun 28 '18 at 22:10
1
Tried that with IntelliJ, no results. Which is why I'm confused I keep getting that warning, and would be helpful if I could find exactly which file is throwing it
– Justin
Jun 28 '18 at 22:26
I am experiencing the same issue. I assume this is from a dependency, but I'm at a loss to determine which one.
– Zach
Jan 3 at 1:52
add a comment |
A naive project-wide search forReact.PropTypesmight just work?
– Tholle
Jun 28 '18 at 22:10
1
Tried that with IntelliJ, no results. Which is why I'm confused I keep getting that warning, and would be helpful if I could find exactly which file is throwing it
– Justin
Jun 28 '18 at 22:26
I am experiencing the same issue. I assume this is from a dependency, but I'm at a loss to determine which one.
– Zach
Jan 3 at 1:52
A naive project-wide search for
React.PropTypes might just work?– Tholle
Jun 28 '18 at 22:10
A naive project-wide search for
React.PropTypes might just work?– Tholle
Jun 28 '18 at 22:10
1
1
Tried that with IntelliJ, no results. Which is why I'm confused I keep getting that warning, and would be helpful if I could find exactly which file is throwing it
– Justin
Jun 28 '18 at 22:26
Tried that with IntelliJ, no results. Which is why I'm confused I keep getting that warning, and would be helpful if I could find exactly which file is throwing it
– Justin
Jun 28 '18 at 22:26
I am experiencing the same issue. I assume this is from a dependency, but I'm at a loss to determine which one.
– Zach
Jan 3 at 1:52
I am experiencing the same issue. I assume this is from a dependency, but I'm at a loss to determine which one.
– Zach
Jan 3 at 1:52
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f51091781%2fwhere-can-i-find-out-where-the-react-proptypes-warning-is-coming-from%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f51091781%2fwhere-can-i-find-out-where-the-react-proptypes-warning-is-coming-from%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
A naive project-wide search for
React.PropTypesmight just work?– Tholle
Jun 28 '18 at 22:10
1
Tried that with IntelliJ, no results. Which is why I'm confused I keep getting that warning, and would be helpful if I could find exactly which file is throwing it
– Justin
Jun 28 '18 at 22:26
I am experiencing the same issue. I assume this is from a dependency, but I'm at a loss to determine which one.
– Zach
Jan 3 at 1:52