turbo: regression: turbo couldn't find packages

What version of Turborepo are you using?

1.1.5

What package manager are you using / does the bug impact?

Yarn v1

What operating system are you using?

Linux

Describe the Bug

I upgraded turbo to 1.1.5 then tried to run turbo run build on my server and it couldn’t find packages, output below.

• Packages in scope: 
• Running build in 0 packages

 Tasks:    0 successful, 0 total
Cached:    0 cached, 0 total
  Time:    83ms >>> FULL TURBO

Expected Behavior

find packages, and run pipeline.

To Reproduce

it was run on Debian 11 with node 16, and latest yarn.

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 1
Comments: 15 (10 by maintainers)

Most upvoted comments

@dulmandakh Just wanted to check in, did you manage to get your dependencies picked up? If you want to use the latest canary, you should be able to use --dry to check what would be run.

gsoltis on Mar 21, 2022

The package itself can be named test, just not the folder it lives in

jaredpalmer on Mar 14, 2022

Correction: You cannot have package in a directory named test. https://github.com/vercel/turborepo/blob/main/cli/internal/context/context.go#L475-L482 This is to comply with pnpm which uses the same ignores patterns we use https://github.com/pnpm/pnpm/blob/917b95c01fd4e6b347dd6159506756693dc051ec/packages/find-packages/src/index.ts#L8-L11

jaredpalmer on Mar 14, 2022

@jaredpalmer

This is how we define packages, also we use * to specify local dependency.

 "workspaces": [
    "packages/*",
    "sites/*"
  ],

dulmandakh on Mar 11, 2022