Worms David
Worms David
I reproduce your [code sample](https://github.com/adaltas/node-csv/blob/master/demo/issues-esm/labo/361-transform-memory.js). With the latest source code, the memory usage stays between 20MB and 30MB on a 30GB generated CSV file. Maybe some change since your report...
@dmurvihill Could you have a look at the latest release of stream-transform version 3.2.10. It now takes the return value from `push` into account to throttle the execution. Based on...
I didn't reproduce the pausing behavior. I will need to dig more into it. Any change you could reproduce the pausing in [my sample](https://github.com/adaltas/node-csv/blob/master/demo/issues-esm/labo/361-transform.js) ?
Closing for lack of activity
Then I propose to update this PR to apply `const` to every option.
Shall be the right time now that Gatsby v2 is release. Could you provide an update ?
1. Could you add a unit test (you could submit it in js if not confortalbe with coffee) to your merge request ? 2. "When I used the "cast" example...
I enriched the [cast documentation page](https://csv.js.org/parse/options/cast/) with a new usage sample that preserve a value as is. Hopefully it will answer your concern. Otherwise feel free to open a new...
While I am not against the idea, I can't say that I fully support the idea. However, if you come up with a clean `delimiter_auto` option, I'll probably merge it.
I would tend to discover the character, like in the second methods, after filtering any already used character in options (eg quotes, row delimiters, ...) and general ascii characters ([a-zA-z0-9])...