The ESLint plugin should have a rule for enforcing the order of properties in MessageDescriptor objects. The order should be autofixable. It would work beautifully with auto generating IDs wit enforce-id. Currently the id is inserted as the last property, but it would make sense to have it as the first instead.

The logical order would be the one defined in MessageDescriptor interface:

export interface MessageDescriptor {
    id?: MessageIds;
    description?: string | object;
    defaultMessage?: string | MessageFormatElement[];
}

TanStack does something like this, so it would probably be pretty easy to copy their implementation. See: https://tanstack.com/router/latest/docs/eslint/create-route-property-order