I have a repo containing subdirectories for each part of the project (back, front, etc.). The serverless part is in the

back/

subdirectory. Inside this subdirectory is a yarn mono-repo, with all dependencies installed at

back/

level. To make Seed installing dependencies, I copy the package.json and yarn.lock files at the root level during the 'before compile' step of the Seed.yml. I don't know why, but Seed decided to install dependencies using npm instead of yarn, despite the yarn.lock file. Any idea why? Or any way to force Seed using yarn?

Hey @Maxime, SEED decides what packager at the very beginning of the build process, before getting to the

Compile

step.

Thanks for the explanation @Frank. I only have it at the

back/

level, as no dependencies are installed at the root level and each Yarn workspace only has a package.json file

If u have

yarn.lock

at the service level ie.

back/

, Seed should use Yarn.

Ah.. I see. So the services are inside the subdirectories of

back/

Thanks for the investigation, i'll try it!