-
Hi, I'm using Crawlee's Puppeteer crawler I've imported crawlee via package.json like {
"crawlee": "^3.5.4"
} Shall I be importing puppeteer in via my package.json as well? I see puppeteer in crawlee's peer dependency but as optional https://www.npmjs.com/package/crawlee?activeTab=code Issue is that puppeteer gets bumped very often with bug fixes and I've been stuck with puppeteer 21.1.x since I've imported it in my package.json. Ideal expectation is that I just import Crawlee and bumping Crawlee bumps puppeteer as well as per its requirements/support. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
Also on github puppeteer dev devenpency is ^21.2.1 https://github.com/apify/crawlee/blob/master/package.json#L97 However on npm it is <=21.1 https://www.npmjs.com/package/@crawlee/puppeteer?activeTab=code |
Beta Was this translation helpful? Give feedback.
-
its a peer dependency, you are responsible to install it and manage its versions, we dont want to dictate what version of puppeteer you want to use. |
Beta Was this translation helpful? Give feedback.
-
I get this error when i try to bump puppeteer
|
Beta Was this translation helpful? Give feedback.
you can install any version, this is just npm constraints check you can get around via some option