Context
Crawlee for Python already supports choosing from multiple package managers (pip, uv, poetry) when scaffolding a new project. The Apify Actor templates should offer the same flexibility (for both Python and JS/TS) to provide a better DX.
Goal
When creating a new JS/TS Actor based on the Actor template, users should be able to choose their preferred package manager (npm, yarn, pnpm, bun - decide which makes sense).
Each option should generate the appropriate lock file (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb) and configure the Dockerfile/build accordingly.
Potential roadblocks / coordination
- Apify CLI — Add support for package manager choice.
- Apify Console — The Console's "Create Actor" flow and any template selection UI need to support the package manager choice as well.
Reference
Context
Crawlee for Python already supports choosing from multiple package managers (
pip,uv,poetry) when scaffolding a new project. The Apify Actor templates should offer the same flexibility (for both Python and JS/TS) to provide a better DX.Goal
When creating a new JS/TS Actor based on the Actor template, users should be able to choose their preferred package manager (npm, yarn, pnpm, bun - decide which makes sense).
Each option should generate the appropriate lock file (
package-lock.json,yarn.lock,pnpm-lock.yaml,bun.lockb) and configure the Dockerfile/build accordingly.Potential roadblocks / coordination
Reference