React Hooks Error: Hooks can only be called inside the body of a function component

后端 未结 17 2073
旧巷少年郎
旧巷少年郎 2020-12-05 04:07

I am getting this error when using the useState hook. I have this in it\'s basic form, looking at the react docs for a reference, but am still getting this erro

相关标签:
17条回答
  • 2020-12-05 04:26

    Updated: 2018-Dec

    New version of react-hot-loader is out now, link. Hooks is now working out of the box. Thank to the author, theKashey.

    Check out this boilerplate https://github.com/ReeganExE/react-hooks-boilerplate

    • React Hooks
    • React Hot Loader
    • Webpack, Babel, ESLint Airbnb

    Previous Answer:

    First, make sure you installed react@next and react-dom@next.

    Then check for you are using react-hot-loader or not.

    In my case, disable hot loader & HMR could get it work.

    See https://github.com/gaearon/react-hot-loader/issues/1088.

    Quoted:

    Yes. RHL is 100% not compatible with hooks. There is just a few reasons behind it:

    SFC are being converted to Class components. There is reason - to be able to forceUpdate on HMR, as long there is no "update" method on SFC. I am looking for other way of forcing the update (like this. So RHL is killing SFC.

    "hotReplacementRender". RHL is trying to do React's job, and render the old and the new app, to merge them. So, obviously, that's broken now.

    I am going to draft a PR, to mitigate both problems. It will work, but not today.

    There is a more proper fix, which would work - cold API

    You may disable RHL for any custom type.

    import { cold } from 'react-hot-loader';
    
    cold(MyComponent);
    

    Search for "useState/useEffect" inside component source code, and "cold" it.

    Updated:

    As per updated from react-hot-loader maintainer, you could try react-hot-loader@next and set the config as bellow:

    import { setConfig } from 'react-hot-loader';
    
    setConfig({
      // set this flag to support SFC if patch is not landed
      pureSFC: true
    });
    

    Thank to @loganfromlogan for the update.

    0 讨论(0)
  • 2020-12-05 04:28

    My problem was forgetting to update react-dom module. See issue.

    0 讨论(0)
  • 2020-12-05 04:28

    Another solution if you are running into this when using npm link:

    You can npm link react in your library as explained here: https://reactjs.org/warnings/invalid-hook-call-warning.html#duplicate-react

    or set react in your library as peerDependency and then use npm link --only=production

    0 讨论(0)
  • 2020-12-05 04:30

    Well in my Case i was calling useSelector inside useEffect !!

    0 讨论(0)
  • 2020-12-05 04:31

    update package.json react-dom version as react

    0 讨论(0)
提交回复
热议问题