Using node for scraper instead of tsx

Author: Aayush-Agnihotri

docker-compose.yml

@@ -1,6 +1,8 @@
+version: '3.8'
+
 services:
   app:
-    image: cornellappdev/eatery-blue:${IMAGE_TAG}
+    image: cornellappdev/eatery-blue-dev:${IMAGE_TAG}
     volumes:
       - ./firebase-service-account.json:/app/firebase-service-account.json:ro
     env_file: .env
@@ -12,12 +14,12 @@ services:
       - scraper
 
   scraper:
-    image: cornellappdev/eatery-blue:${IMAGE_TAG}
+    image: cornellappdev/eatery-blue-dev:${IMAGE_TAG}
     env_file: .env
     networks:
       - eatery-network
     command: ["sh", "-c", "npx prisma migrate deploy && npm run scrape:scheduled"]
 
 networks:
   eatery-network:
-    driver: bridge
+    driver: overlay

package.json

@@ -12,7 +12,7 @@
     "lint": "eslint '{src,test}/**/*.ts' --fix",
     "format": "prettier --write '{src,test}/**/*.ts'",
     "scrape": "tsx prisma/scraper.ts",
-    "scrape:scheduled": "SCHEDULED_MODE=true tsx prisma/scraper.ts",
+    "scrape:scheduled": "SCHEDULED_MODE=true node dist/prisma/scraper.js",
     "studio": "prisma studio"
   },
   "repository": {