We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
*
https://github.com/AlexErrant/turborepo-workspace-bug
^2.3.1-canary.2
CLI: Version: 2.3.1 Path to executable: /home/alex/turborepo-workspace-bug/node_modules/.pnpm/[email protected]/node_modules/turbo-linux-64/bin/turbo Daemon status: Not running Package manager: pnpm Platform: Architecture: x86_64 Operating system: linux WSL: true Available memory (MB): 17335 Available CPU cores: 12 Environment: CI: None Terminal (TERM): xterm-256color Terminal program (TERM_PROGRAM): unknown Terminal program version (TERM_PROGRAM_VERSION): unknown Shell (SHELL): /usr/bin/zsh stdin: false
Running e.g. turbo build in a workspace project should work, even if it doesn't have a wildcard, like in vite-project/ below:
turbo build
vite-project/
packages: - apps/* - packages/* - vite-project/
~/turborepo-workspace-bug/vite-project main ❯ turbo build 98% ╭──────────────────────────────────────────────────────────────────────────╮ │ │ │ Update available v2.1.1 ≫ v2.3.0 │ │ Changelog: https://github.com/vercel/turborepo/releases/tag/v2.3.0 │ │ Run "npx @turbo/codemod@latest update" to update │ │ │ │ Follow @turborepo for updates: https://x.com/turborepo │ ╰──────────────────────────────────────────────────────────────────────────╯ WARNING No locally installed `turbo` found. Using version: 2.1.1. turbo 2.1.1 × missing packageManager field in package.json
This error message is somewhat misleading.
git clone https://github.com/AlexErrant/turborepo-workspace-bug && cd turborepo-workspace-bug && pnpm i && cd vite-project && turbo build
I'm guessing this LOC here is the culprit (or at least part of the problem), since vite-project/ is literally not a file.
The text was updated successfully, but these errors were encountered:
docs/pnpm-workspace_yaml.md
Thank you for the report. This is the same issue as #8599 so I will be closing this in favor of that.
TL;DR our workspace globbing codepath differs slightly from our "am I in this workspace" check in a way that isn't super easy to resolve.
Closing in favor of #8599
Sorry, something went wrong.
No branches or pull requests
Verify canary release
Link to code that reproduces this issue
https://github.com/AlexErrant/turborepo-workspace-bug
Which canary version will you have in your reproduction?
^2.3.1-canary.2
Enviroment information
Expected behavior
Running e.g.
turbo build
in a workspace project should work, even if it doesn't have a wildcard, like invite-project/
below:Actual behavior
This error message is somewhat misleading.
To Reproduce
git clone https://github.com/AlexErrant/turborepo-workspace-bug && cd turborepo-workspace-bug && pnpm i && cd vite-project && turbo build
Additional context
I'm guessing this LOC here is the culprit (or at least part of the problem), since
vite-project/
is literally not a file.The text was updated successfully, but these errors were encountered: