The latest updates on your projects. Learn more about Vercel for Git ↗︎

How would you rewrite this command to use --filter to avoid the deprecated arguments?
turbo run build --cache-dir=.turbo-cache --include-dependencies --no-deps or
turbo run build --cache-dir=.turbo-cache --include-dependencies

Maybe worth it to add these to the docs or in the blog post?

@weyert In your examples, there is nothing scoping down the selection, build will run on every package. Did you mean to include a --scope?

The 1.1 blog mentions partial support for yarn 2+ (nodeLinker: node-modules only), is it worth adding a note about yarn 2+ with the PnP linker now being supported for the run command, but that prune is still not fully supported?

@jaredpalmer Is there something data-specific you were hoping I could contribute to this MR or did you just need another set of eyes?

@acviana No, I think you were erroneously asked for a review, sorry about that

@weyert In your examples, there is nothing scoping down the selection, build will run on every package. Did you mean to include a --scope?

@gsoltis Yes, but is --include-dependencies not deprecated now?

The documentation says:

--include-dependencies is deprecated in 1.2.x. Please use --filter instead.

So my question how can I use --include-dependencies when I don't want to filter a package when I can't use the deprecated --include-dependencies? As the default is false` for this flag

@weyert --include-dependencies is indeed deprecated. You can achieve the same behavior in --filter with --filter=my-pkg...

Maybe the source of confusion is that, without supplying --filter (or --scope, or --since), turbo will run against every package. In both of your examples, you are running build against every package, since you are not providing --filter, --scope, or --since. Any dependencies that would be included with --include-dependencies are already included.

My expectation is that there are very few situations where you will need to include dependencies, either via the deprecated flag or even via a filter, because usually your pipeline takes care of defining the dependencies for you. So with a pipeline where build depends on ^build, turbo run build --filter=my-app will build my-app and all of its dependencies.