jsx-key Missing "key" prop for element in array when there is no array/iteration

[alicerocheman]

Hello,

I just upgraded eslint-plugin-react from 7.28.0 to 7.29.0

The result is I now get a Missing "key" prop for element in array error on all my components, regardless of them having an array/map or anything that would require a key prop.

Before upgrade, the app worked fine, the key prop was already where it should be, on all arrays/lists.

Example of error:

  17:7  error  Missing "key" prop for element in array  react/jsx-key

=> no array on line 17 char 7, just calling a component.

[erikpukinskis]

I can confirm I'm seeing this with [email protected] downgrading to 7.28.0 the error goes away.

[martinstark]

Same, does not look right. Several hundred errors. Some lines trigger this error multiple times.

[yoyo837]

Same here.

[DominicLi77]

I also encountered the same problem, it can be solved by downgrading the version

[shiftj18]

+1，expect it rollback to 7.28.0.

[awmleer]

Wondering why there is no release log about 7.29.0 on the releases page. 🤔

[kliehm]

I do use keys, but of course only for the outmost element. This new rule requires a key for every child element, too. I think this is an error. In the following example the rule throws an error that the div element doesn't have a key attribute. That's wrong.

{this.myArray.map((item) => (
  <li key={item.id}>
    <div>foo</div>
  </li>
)

[shrijan00003]

Wondering why there is no release log about 7.29.0 on the releases page. 🤔

True!,

[cojoclaudiu]

I confirm same issue, I'm using vite with React TypeScript

[sanjeevkpandit]

Facing the same with React.

[briantuju]

Just installed a new project using npx create-next-app and I'm getting the exact same error

[mustafasavul]

We are currently getting the same error in bitbucket pipelines.

When installed with yarn, the package eslint-plugin-react goes up to 7.29.

It gives error like this.

When we do npm install, it does not give an error. Because it stays at 7.28.

[jukialen]

Hey, I tried to find eslint-config-next repositories, because I have the same bug. I updated this and next to latest stable and canary version, but it didn't help. What do you know something about this?

[ljharb]

@jukialen please file a new issue if you're still having problems.

[DanielBailey-web]

Just a quick heads up to anyone still experiencing this after upgrading. You may have to delete your .next folder after upgrading to 7.29.1

[jukialen]

Just a quick heads up to anyone still experiencing this after upgrading. You may have to delete your .next folder after upgrading to 7.29.1

I only add that if someone has only next and eslint-config-next in a package.json, and updating next canary version won't help, it schould delete .next folder, reopen a project and install eslint-plugin-react in 7.29.1 (in this order). It helped me so maybe it'll help someone.

[shaharyar007]

I know it's a bit late, as many of you found the solution probably but I want to add my experience,i was facing the same problem but then I used React fragment (<></>) and the error was removed.