Last header field gets double-quoted (unexpected)

Using 1.12.0 here, seeing a weird issue. If to project this problem on the sample:

var csv = require('csv-parser')
var fs = require('fs')

fs.createReadStream('some-csv-file.csv')
  .pipe(csv())
  .on('data', function (data) {
    console.log('Name: %s Age: %s', data.NAME, data.AGE)
  })

if AGE is the last header field, it’s not possible to access it via data.AGE, but it is possible to access it via data['"AGE"']. What’s more interesting is that it happens only with the last header field. So, as a workaround it’s possible to add a comma at the end of the header field (which adds a new, zero-length header field). This gets data.AGE (or data['AGE']) to return the expected value.

Anyone else seen this issue?

[Dastari]

I had a similar issue with the first header field. The object returned ended up looking like this:

Row { ' ID': '', PHOTOS: '28', TOWN: '', MAP: '', AKA: '', SUBURB: '', ADDRESS: '', HERITAGE: '', NAME: '', DENOMINATION: '', CHECKED: '', CORRECTED: '', NOTES: '', LOCATION: '' }

The issue was the original source CSV from excel was saved with a Byte order Mark which added a character at the start of the file. I suspect your source file may have a non recognized line break character at the end of your header line (or may have Carriage Return and Line Break)

It may be worth opening it in notepad and re-saving it or trying setting the raw: false constructor option or trying newLine: ‘\r\n’

Or just download TextEdit and open the file then re-save it using another encoding (which is what I ended up doing)

[jdevost]

I had the same issue with Byte order Mark. On a Mac, you can clean up your CSV files using this command in a terminal: sed $'s/\xEF\xBB\xBF//g' file.csv