Interesting that Kerwin Peters is selling it as pure Node with zero deps since most scrapers lean on Puppeteer or Playwright. Curious how long that approach survives before stores start tightening anti bot measures.
E-Commerce Price Monitor Pro
2 Comments
@[Ben Kiehl] You're spot on - most scrapers do rely on those tools, and you're right to be skeptical about longevity.
The zero-deps approach works for now because it's lightweight and flies under the radar, but you're absolutely correct that it's a cat-and-mouse game. When sites update their protections, the scraper needs updates too.
Honestly, it's a trade-off - simpler setup today, but might need more maintenance tomorrow. For basic price tracking it holds up okay, but you're right that it's not as bulletproof as the heavy-duty solutions!
Please log in to add a comment.
Impressive work, eyedolise — love the simplicity of keeping it dependency-free. Using pure Node.js for a production-grade scraper is a bold move that makes setup so lightweight. The tiered pricing and JSON-based configuration also make it very developer-friendly. Curious — have you considered adding proxy rotation or rate limiting support for larger-scale users?
@[Gift Balogun] Thank you! Really appreciate you noticing the design choice behind going dependency-free. You're absolutely right—it's a trade-off between simplicity and robustness.
To answer your question: Yes, proxy rotation and more granular rate-limiting are 100% the next features on the list.
Right now, the script has basic rate-limiting (2000ms+ between requests per domain), but for heavy use, it needs:
· Configurable proxy lists in websites.json
· IP rotation to avoid blocks
· Exponential backoff on failures
· User-agent cycling
I kept V1 simple to solve the 80% use case, but you've nailed the exact needs for the 20% doing large-scale monitoring. Those features will likely land in V2 soon.
Thanks again for the sharp feedback—means a lot coming from someone who gets the technical balance!