Worms David

Summer cleanup. Closing for lack of activity.

I suggested to handle the feature in the application code. The feature might never be accepted in the parser. Note I could change my mind.

Sorry for the very large response delay, closing because unless I am mistaken, I don't see column as a property of info. Please re-open if I am wrong.

I am looking at it as well, trying to read the official doc and extract some sense. Using the more robust strategy of try-and-fail, I get to the same conclusion,...

Instead of ``` parser.on('end', parser.destroy); ``` Try ``` parser.end() parser.on('end', parser.destroy); ``` This seems to prevent the `ERR_STREAM_PREMATURE_CLOSE` error in my test

It is also associated with the `close` event which is not thrown unless `destroy` is called or unless there is an error.

The all stream API is hard to grasp. I am not even sure whether the `close` event is expected to be called or not. Anyway, new versions are published: -...

Can you go inside the source code of the parser and add a condition, for example ```js if (this.destroy !== undefined) { this.on('end', this.destroy); } ``` I would also need...

I am re-opening this issue. I did some testing after issue #410. Issue #333 is fixed with `this.end(); this.destroy();` Issue #410 is fixed with `this.end(); this.on('end', this.destroy);` 1. It happens...

The [win2.csv](https://github.com/rahulgolwalkar/csv_parser_windows_test_delete/blob/main/win2.csv) file used for testing contains two record delimiter, `\r\n` and `\r`. When the option is auto-discovered, the first one to appear, `\r\n` in this case, defined the value...