Thanks for the PR. I think, instead of an error, any primitive could be wrapped into an object with an id.

Example:

[ "foo" ] -> [ { id: "...", value: "foo" } ]

Great work, and I think there can be one more edge case - we should also guard nested arrays.

In JS, arrays are objects, so a check like typeof item === 'object' && item !== null still allows []. Those entries can then get an id assigned and continue as if they were valid records.

Would it make sense to tighten the condition to explicitly reject arrays as well?

if (typeof item !== 'object' || item === null || Array.isArray(item)) {
  throw new Error(/* existing helpful message */)
}

Potential solution can be - also reject Array.isArray(item) in the validation guard so only plain object entries are accepted?