The out directory will be created fine, with also a json sub-directory within it.
Now my question is: Why does the out/json directory also contain the pnpm-lock.yaml and pnpm-workspace.yaml files? These are clearly not a json file? Is this a bug in of turbo prune command? Since the same yaml files are present in the out directory as well.
I don’t get it.. . Should I now copy the yaml files from the out directory or the yaml files from the out/json sub-directory? They seem to be identical, but I would like to know it for the future (in case this incorrect way will be removed/fixes).
The out/json directory name is a maybe bit misleading. It’s not exclusively for JSON files.
This directory contains all the package metadata and lockfiles needed for dependency installation. When you’re using pnpm, that includes YAML files like pnpm-lock.yaml and pnpm-workspace.yaml.
This is the expected behavior, not a bug. The structure is designed this way to separate:
out/json/ - Package metadata and lockfiles (for dependency installation)
out/full/ - The complete pruned source code (for the build step)
This separation allows for efficient Docker layer caching where you can install dependencies first using files from out/json, then copy and build the source code from out/full.
. Should I now copy the yaml files from the out directory or the yaml files from the