React For loop component
This approach is not bad but I'd highlight a few issues:


You wrap each element with a &lt;div&gt;, it's unnecessary and for a very long list you create many useless elements. This also prevents &lt;RFor&gt; to be conveniently used (for example) to generate rows in a table.
You're assigning data to the properties of each item. While this might be convenient it's also fragile: what if an object as a property named key, or children, ref or...anything else already used? I'd assign data to a single property.
const { items } = props || [] does not do what you, probably, think it's doing. [] won't be the default if items is falsy but the default if props is falsy. The correct syntax, if the value is undefined is const { items = [] } = props;. If you want to handle also null then you can't destructure: const items = props.items || [];.
To use index as key is, more often than not, a terrible idea if the list isn't fixed (for example if you can remove/add elements anywhere in the list). Leave this responsibility to the caller because it's the only one with enough knowledge to pick a sensible unique ID (which in some very specific cases can even be the index).
You're passing props.children directly to React.cloneElement however it expects a single element and children can be an array. Enforce this rule using React.only().


To put things together (leaving out the key for the moment):

const RFor = props =&gt; {
    const items = props.items || [];
    return items.map(data =&gt; React.cloneElement(React.only(props.children), { data });
};


All these said you may start wondering if you even need RFor, let's compare with few alternatives:

&lt;RFor items={TEMP_DATA_ARRAY}&gt;
    &lt;Item /&gt;
&lt;RFor&gt;


Vs

{TEMP_DATA_ARRAY.map(data =&gt; &lt;Item key={data.id} {...data} /&gt;)}


Or:

{TEMP_DATA_ARRAY.map(data =&gt; &lt;Item key={data.id} data={data} /&gt;)}


I don't see any benefit (note that you may, instead of children use a property like:

&lt;RFor items={TEMP_DATA_ARRAY} component={Item} /&gt;


Also note that to solve the key problem you might use a render function:

&lt;RFor items={TEMP_DATA_ARRAY}&gt;
    {data =&gt; &lt;Item key={data.key} data={data} /&gt;}
&lt;RFor&gt;


RFor IMHO makes sense only if it adds any other value over map(), it might be filtering or it might be part of an abstraction to build a presentation component with templates (with properties like controlTemplate, headerTemplate and itemTemplate as you often see in WPF).