Piero Maddaleni

@pedroelbanquero if you look into the `main.js` file you can see any command line arguments you can use

Also about those command line arguments, one thing that I've noticed is that they don't even seem to work half of the time.

I am having the same problem. Combing through the code and adding comments at key points, I seem to have narrowed down the issue to something with the `gtfs-stream` library...

Whoops, forgot to add this. The loader gets initialized, but never seems to resolve the promise. 

With even more testing, this is definitely a bug with `gtfs-stream`. Tried doing a test with this script: ```js const fs = require('fs'); const gtfs = require('gtfs-stream') fs.createReadStream("gtfs.zip") .pipe(gtfs()) .on('data',...

Doing some more poking around, it seems like `gtfs-stream` sends a `finish` event instead of an `end` event (what raptor is expecting). Doing this allowed the gtfs to load, but...

Yeah that's true. Lemme add in a listener for errors really quick then.

Hmmmm, no errors seem to be passed down. Something is going wrong somewhere but nothing is logging that.

Submitted an issue to gtfs-stream https://github.com/staeco/gtfs-stream/issues/7 Now, there might be further issues with this, as poking through the code, it seems like the 4th item passed to `RaptorAlgorithmFactory.create()` is meant...

TBH the solution to the dates shouldn't be to change the type to a string, but to ensure it is a Date before being returned.