strict mode emit error

• Operating System: WSL
• Node Version: 15.8
• NPM Version: 7.5.1
• csv-parser Version: 3.0.0

Expected Behavior

Not sure

Actual Behavior

It appears, a range error event is emitted when strict mode is enabled, which can be listened with the on("error") as usual.

However, when this range-error event is emitted, nodejs never emits the on("end") and on("close"). I'm assuming this has something to do with the transform being broken. This doesn't affect the process most of the time, file executes and exits fine but if you need to do cleanup, it could be problematic as it was in my case, where I needed to disconnect the db once the readstream has finished.

Changing the emitted event from error to anything worked and also fired the end and close. Please the sample file and script below to produce the issue. Although I'm not positive if the way it is now is the expected way.

Perhaps something is needed in the transformer to handle this, if not and it's okay, I recommend changing the error to line-error since this is not really a stream related error.

       if (!skip && this.options.strict && cells.length !== this.headers.length) {
            const e = new RangeError("Row length does not match headers");
            this.emit("error", e);

How Do We Reproduce?

head1,head2,head3
a,b,c
x,x,x
e,e
y,y,y
f,f

const csvParser = require("csv-parser");
const fs = require("fs");

const rs = fs.createReadStream("./a.csv");

rs.pipe(
    csvParser({
        strict: true,
    })
)
.on("error", () => {
    console.log('caught');
})
.on("end", function () {
    console.log("All the data in the file has been read");
})
.on("close", function (err) {
    console.log("Stream has been destroyed and file has been closed");
});

Start at the strict-mode branch that emits the RangeError and follow the csvParser stream through the error, end, and close handlers in the reproduction. Run the provided CSV and Node script, then verify the intended terminal-event behavior for malformed rows.