#pnpm dlx trigger.dev@beta deploy in uses npm instead of pnpm
1 messages · Page 1 of 1 (latest)
Any chance you could temporarily disable the preinstall script that enforces pnpm to see if it deploys successfully with npm instead?
yes that does work but I want it to work via pnpm also not npx.
We generate a minimal set of dependencies required for your tasks that we install with npm. Are you worried something is going to break if we don't use pnpm? The resolution step is already done with your package manager of choice, i.e. pnpm.
Ideally I don't want to remove preinstall every time I try to deploy.
We're going to release a new version of the CLI in a couple of weeks and we won't be running any scripts from the package.json anymore.
Out of interest, why do you use that allow-only script? Is it because you have other contributors who use the wrong package manager and commit the artifacts?
This is how we do this: https://github.com/triggerdotdev/trigger.dev/blob/c1d4c04e898bbf69348269a986217b088a188a96/package.json#L64
No. I had an experience before where other devs ran into issues when using a different package manager, and we spent some time figuring that out. We do have packageManager specified in package.json, but for some reason npm still goes through.