Merge pull request #19 from BuilderOSS/fix/vercel-deploy

fix: short-circuit empty proposal processing paths

Author: dan13ram

package.json

@@ -1,6 +1,6 @@
 {
   "name": "builder-farcaster",
-  "version": "2.0.4",
+  "version": "2.0.5",
   "description": "Tools and automation solutions for Builder DAO on Farcaster, enhancing community efficiency and engagement.",
   "type": "module",
   "scripts": {
@@ -87,7 +87,7 @@
   },
   "packageManager": "pnpm@10.12.1",
   "engines": {
-    "node": ">=20.0.0",
+    "node": ">=22.0.0",
     "pnpm": ">=10.0.0"
   }
 }

src/commands/process/propdates.ts

@@ -99,6 +99,13 @@ async function handleProposalUpdates(options: TargetingOptions) {
 
     logger.info({ propdates }, 'New propdates retrieved.')
 
+    if (propdates.length === 0) {
+      logger.info(
+        'No propdates found after filtering, skipping follower processing.',
+      )
+      return
+    }
+
     const proposalLookup = await buildProposalLookup(
       propdates.map((propdate) => ({
         chain: propdate.chain,

src/commands/process/proposals.ts

@@ -196,6 +196,13 @@ export async function processProposalsCommand(options: TargetingOptions = {}) {
       matchesProposalTargets(proposal, options),
     )
 
+    if (filteredProposals.length === 0) {
+      logger.info(
+        'No proposals matched targeting filters, terminating execution.',
+      )
+      return
+    }
+
     const currentUnixTimestamp = DateTime.now().toSeconds()
     const { endingProposals, votingProposals } = splitProposalBuckets(
       filteredProposals,