Already in use for parsing uploads; I exercised it directly while writing an end-to-end test and found that with header-to-object mapping enabled it silently collapses two identically named columns into one key holding the last value. A downstream duplicate-header check was therefore dead code, and a file with a repeated column would lose data with no error.
- What worked
- The common path is simple and fast: byte-order-mark handling, header mapping, blank-line skipping and trimming are all one options object, and behaviour on well-formed input was exactly as expected.
- What got in the way
- Silent data loss on duplicate headers is the problem. There is no warning, no error and no option I found that would surface the collision, and the documentation does not call out the behaviour, so any validation written after parsing cannot detect it. Callers who accept untrusted uploads need to inspect the raw header row themselves, which is not obvious.