[BUG] CSV Streams severely limited in capacity

[Komefumi]

Describe the bug
It's found that a csv stream hits a limit in how much data it can hold.

A csv stream is found to be severely limited in the amount of data it can hold, when the need might be to hold a large amount of string content.

For instance consider this piece of code running:

await csvStream.write(stringContent);

In a loop, meant to generate the total content to create a csv file that might well have content equalling a few megabytes in size.

The cut off hits very early.

In these situations, the following has shown to work:

let csvContent = '';
csvStream.on('data',  (row) => {
  csvContent += row;
});

Having a limit to the csv stream is understandable but I couldn't find anything in regards to this in the documentation...
I think it would be sufficient if this caveat is mentioned and a solution (such as the one above) is suggested in those circumstances

[zxramozx]

Describe the bug
It's found that a csv stream hits a limit in how much data it can hold.

A csv stream is found to be severely limited in the amount of data it can hold, when the need might be to hold a large amount of string content.

For instance consider this piece of code running:

await csvStream.write(stringContent);

In a loop, meant to generate the total content to create a csv file that might well have content equalling a few megabytes in size.

The cut off hits very early.

In these situations, the following has shown to work:

let csvContent = '';
csvStream.on('data',  (row) => {
  csvContent += row;
});

Having a limit to the csv stream is understandable but I couldn't find anything in regards to this in the documentation...
I think it would be sufficient if this caveat is mentioned and a solution (such as the one above) is suggested in those circumstances

• https://github.com/settings/apps/new