Adding Pino logs

[resurl]

Changes

• logger pretty prints when process.env.NODE_ENV === "development"

under /server

• set ESLint no-console rule to true
• added RUN field in Dockerfile to install Chromium. this was a bug i didn't catch when we first started using Docker
• ignored scraper output files because running nodemon on the scraper would cause infinite restarts
• added Pino logger, replaced all console statements to use the logger instead

under /client

• set ESLint no-console rule to true
• add Pino logger to be imported, in case logging is needed

Motivation and Context

having logs instead of using console.log allows us to debug with richer information. with pino, we can potentially filter logs by log level (for example, only seeing ERROR messages if any, or taking out DEBUG messages when needed). it also allows us to keep track of metrics down the road.

How Has This Been Tested?

• tested on both Docker and local setup + ran a scraper test to test log levels, both work as expected

Screenshots (if appropriate):

Related Issues

• Closes issue Use a proper Logger instead of console.log #18

[resurl]

@yehee i added something to the Dockerfile if you want to take a look, in case you were wondering why i requested you LOL.

[johnagl]

I'm getting this error for some reason. Package.json has the correct dependency. Looking into it..

Looks like the node_modules line in volumes of server was causing it. I'm not sure why. Have to look into it more.

[johnagl]

Looks good overall!

[yehee]

I'm getting this error for some reason. Package.json has the correct dependency. Looking into it..

Looks like the node_modules line in volumes of server was causing it. I'm not sure why. Have to look into it more.

@johnagl Bumped into this issue just now, has this been resolved?