Parsing remote files with download: true always fails, attempts to parse the URL itself

[mtchllbrrn]

Sample code:

Papa.parse('http://samplecsvs.s3.amazonaws.com/SalesJan2009.csv', {
  download: true,
  complete: function(results) {
    console.log(results);
  }
})

Returns:

{ data: [ [ 'http://samplecsvs.s3.amazonaws.com/SalesJan2009.csv' ] ],
  errors:
   [ { type: 'Delimiter',
       code: 'UndetectableDelimiter',
       message: 'Unable to auto-detect delimiting character; defaulted to \',\'',
       row: undefined } ],
  meta:
   { delimiter: ',',
     linebreak: '\n',
     aborted: false,
     truncated: false } }

[bewallyt]

I'm getting the same error. Were you able to find a solution?

[mtchllbrrn]

Unfortunately not. My needs changed shortly after I stumbled upon this bug, which obviated the need to come up with a solution.

[rozklad]

looks like it works good on client side, but does what you describe on server side

[allenfuller]

I keep running into this myself. Have tried both calling a file from S3 and a local file, but either option just returns:

Parsing complete:
{ data: [],
  errors: 
    [ { type: 'Delimiter',
        code: 'UndetectableDelimiter',
        message: 'Unable to auto-detect delimiting character; defaulted to \',\'',
        row: undefined } ],
   meta: 
    { delimiter: ',',
      linebreak: '\n',
      aborted: false,
      truncated: false,
      fields: [ 'http://s3.amazonaws.com/bucket/file_name.csv' ] } }

[harrisonhunter]

Added this note to the ReadME but wanted to post here in case anyone is subscribed to this thread:

Note: This package is no longer necessary: Note: If you are using a recent version of Meteor or imports, you no longer need this package. You can install the papaparse npm package directly and import it. In the root of your meteor project run meteor npm install --save papaparse. Then, you can import with import Papa from 'papaparse'; or import * as Papa from 'papaparse';

This problem is likely solved by switching to the npm version of the package OR is a problem in the npm version of the package and is thus out of scope for this repo