**Packages**
* `"react": "^16.13.1"`
* `"eslint-plugin-react-hooks": "^4.0.8"`

The issue #18819 still happens with `eslint-plugin-react-hooks@4.0.8`.

Using the example code from the other issue gives the following errors:

![image](https://user-images.githubusercontent.com/37122343/90794940-59d9a980-e305-11ea-9ec0-98f69b41c280.png)

![image](https://user-images.githubusercontent.com/37122343/90795019-770e7800-e305-11ea-92b8-b64407b0b22c.png)


`,
      errors: [
        topLevelError('useState'),
        topLevelError('React.useCallback'),
        topLevelError('useCustomHook'),
      ],
    },
    {
      code: `
        // Technically this is a false positive.
        // We *could* make it valid (and it used to be).
        //
        // However, top-level Hook-like calls can be very dangerous
        // in environments with inline requires because they can mask
        // the runtime error by accident.
        // So we prefer to disallow it despite the false positive.
        const {createHistory, useBasename} = require('history-2.1.2');
        const browserHistory = useBasename(createHistory)({
          basename: '/',
        });
      `,
      errors: [topLevelError('useBasename')],
    },
    {
      code: `
        class ClassComponentWithFeatureFlag extends React.Component {
          render() {
            if (foo) {
              useFeatureFlag();
            }