Open gonzalob opened 4 weeks ago
Want to shed some light on this matter, I think this is a pnpm issue.
A work around is to somehow ignore the postinstall script and manually run it. In my case, I have to fork the repo, rename the postinstall script to "postinstall-custom". Then after pnpm install
, I will go directly to the postman-code-generators and run pnpm postinstall-custom
My setup:
When using '*' as package definition for a pnpm workspace, the post-install script hangs until it triggers an OOM. Looks like it's spawning infinite shells to build itself recursively.
To reproduce:
pnpm store prune
)pnpm install
)