If you write a Node script the prints output to the screen, and try to pipe the output to a file, you can get an error:<\/p>\n
\n$ node extract.js > ideas.csv\noutput is not a tty\n<\/pre>\nIn my case, I was trying to write out a CSV file:<\/p>\n
\nfor (var k = 0; k < all.length; k++) {\n console.log(all[k]); \n}\n<\/pre>\nThe solution to this is to open the file directly and write to it:<\/p>\n
\nvar fs = require('fs');\nvar results = '';\n\nfor (var k = 0; k < all.length; k++) {\n results += all[k] + \"\\n\";\n}\n\nfs.writeFile(\"ideas.csv\", results);\n<\/pre>\nThe reason this doesn't work as expected appears to be that 'git bash' is passing the command through to the Windows cmd shell, and not handling the output stream correctly. Writing directly to a file avoids the issue entirely.<\/p>\n","protected":false},"excerpt":{"rendered":"
If you write a Node script the prints output to the screen, and try to pipe the output to a file, you can get an error: $ node extract.js > ideas.csv output is not a tty In my case, I was trying to write out a CSV file: for (var k = 0; k < … \n\n