-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
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
[turborepo] ERROR run failed: error preparing engine: Missing task definition, configure "build" or "___ROOT___#build" in turbo.json #3050
Labels
kind: bug
Something isn't working
Comments
Looks like it happens when I have this in the root's
In 1.6.3 it gives an error, which I missed, but in 1.7.0 it acts weird:
in 1.7.0:
everything starts work when I change the above to:
|
tknickman
added a commit
that referenced
this issue
Jan 10, 2023
We were unable to parse an npm lockfile that used the alternate format for workspaces (`"workspaces": { "packages": [ "packages/**" ]}`) Error manifested as: ``` WARNING Issues occurred when constructing package graph. Turbo will function, but some features may not be available: 1 error occurred: * json: cannot unmarshal object into Go struct field NpmPackage.packages.workspaces of type []string ``` Fixes #3207 and #3050
@weyert parsing error should be fixed in the latest canary and will go out with our next release |
Great thank you! |
for me it was doing this:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Turborepo are you using?
1.7.0-canary.3
What package manager are you using / does the bug impact?
npm
What operating system are you using?
Mac
Describe the Bug
I tried to upgrade
turbo
from version1.6.3
to1.7.0-canary.3
and since the upgrade it's throwing the following error:while with
1.6.3
it runs as expected:Expected Behavior
I would expect that the command
turbo run build
would succeed runningTo Reproduce
Not available yet
Reproduction Repo
No response
The text was updated successfully, but these errors were encountered: