ContextPipeline is internal, so there is no supported way to put custom members on the crawling context - users have to subclass the crawler. JS v4 exposes an extendContext option that runs before navigation, making its members visible to the navigation hooks and the request handler alike, and additionally lets navigation hooks override context members.
JS implementation: apify/crawlee#3119, apify/crawlee#3672
✍️ Drafted by Claude Code
ContextPipelineis internal, so there is no supported way to put custom members on the crawling context - users have to subclass the crawler. JS v4 exposes anextendContextoption that runs before navigation, making its members visible to the navigation hooks and the request handler alike, and additionally lets navigation hooks override context members.JS implementation: apify/crawlee#3119, apify/crawlee#3672
✍️ Drafted by Claude Code