• constructor names should be capitalized (#L5)
• quote usage should be consistent (#L21-L22, #L31-L33)
• variables declared in methods should not have global scope (#L12, #L122, #L131)
• loop counters should not have global scope (#L27)
• empty cases should be omitted (#L36)
• indentation is missing (#L85-L88)
• excessive nesting should be avoided (#L63-L80)
• dead logic should be corrected (#L85-L88)
• spelling (#L61, #L64)
• consider following a column limit convention
• strict type comparison is preferable (#L63, #L67)
• unused modules should be omitted (#L3-L5)
• error should also dispatch HTTP 500 (#L44)
• consider using res.json() instead of manually setting headers

There are extra quotation marks at the beginning and end of the JSON string, as well as several back slashes ('/') in it. I accounted for this in the extension as a temp fix, but it should be fixed permanently here.

We can also always return it and link it as a source in the extension/front end.

Maybe this could be in the form of finding a material design css framework?

There are errors with callbacks when trying to access /api?auth.....
I might have written variables wrong (not 100% sure when to use var and when not to use it) that may be the problem.
I believe that if we can get it working, then it should be finished (for now)!

Scrape function is pretty ugly. Could be refactored at some point.

It seems that some articles (for example, Albert Einstein) automatically correct for trying to access wikiquote.org/wiki/albert_einstein (note the lower case name), while others do not (for example, Carl Sagan). This means to access Carl Sagan's page, the URL has to be wikiquote.org/wiki/Carl_Sagan, and not wikiquote.org/wiki/carl_sagan. We have to make the first letter capitalized and the letter after a space capitalized in cleanName().

This function is pretty big, and needs to be refactored at some point.

scraper() in lib/scraper.js is pretty big and not very clear. It could use some cleaning up at some point.