fix(scraper-tools): restore saveSnapshot() under content-type v2 - #361
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: apify/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 5 included reviews per hour; 4 remain after this review. 📝 WalkthroughWalkthroughThe crawler now imports and calls the named Merge Risk: ⚪ Minimal · up to The change restores snapshot saving and XML content-type handling with content-type v2 named APIs. No current merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
Comment |
36feb7b to
58595d6
Compare
context: https://apify.slack.com/archives/C09TL7LMJE9/p1788355444863089
content-type v2 marks its CommonJS output
__esModulewithout exporting a default, so__importDefaultleft.defaultundefined and everycontext.saveSnapshot()call threw. A named import emits a plainrequirewith no interop shim. Introduced by the
^1.0.5->^2.0.0bump in #347, shipped to Cheerio and jsdom Scraper in the 2026-08-31 stable builds.