Hi, Justin! Welcome to the Vercel Community

How did you get on with this in the end?

I still haven't solved it. I'm hoping to get some advice from the community, as I have no idea how to approach this problem.

Does anyone have an idea on how to address this? If not, I'll probably just start from scratch with a new project and copy over existing code in chunks. Not sure what else to do.

Hey @pawlean, do you know anyone that could help out on this? Thanks!

@ryandotfurrer @justinsbarrett Apologises for the radio silence! Justin, can you share your package.json with us?

The error message suggests there's an issue with the workspace configuration in your project.

Here are the contents of package.json:

1
{
2
  "name": "loa-portal",
3
  "private": true,
4
  "scripts": {
5
    "build": "turbo run build",
6
    "dev": "turbo run dev",
7
    "lint": "turbo run lint"
8
  },
9
  "devDependencies": {
10
    "turbo": "^2.3.4"
11
  },
12
  "packageManager": "npm@10.5.2",
13
  "workspaces": [
14
    "apps/*",
15
    "packages/*"
16
  ],
17
  "dependencies": {
18
    "convex-helpers": "^0.1.65"
19
  }
20
}

Could you try the following?

1
{
2
  "name": "loa-portal",
3
  "private": true,
4
  "scripts": {
5
    "build": "turbo run build",
6
    "dev": "turbo run dev",
7
    "lint": "turbo run lint"
8
  },
9
  "devDependencies": {
10
    "turbo": "^2.3.4"
11
  },
12
  "packageManager": "npm@10.5.2",
13
  "workspaces": {
14
    "packages": [
15
      "apps/*",
16
      "packages/*"
17
    ]
18
  },
19
  "dependencies": {
20
    "convex-helpers": "^0.1.65"
21
  }
22
}

Exactly the same error as before.

After you made those changes, did you:

• Run npm install or yarn install (depending on which package manager you're using) to ensure all dependencies are correctly installed.
• Try running turbo dev again.

If not, could you try that?

I'm pretty sure that I did, but I just tried it again. The install didn't do anything that I can see, and turbo dev still generates the same error.

Ah, that is tough! Any chance you can share a minimal reproducible example with us?

I may be able to do that, but at this point I'm feeling like starting over might be a more effective use of my time on this particular project. I've got to significantly rework some other stuff anyway (converting the lone app so far from Remix to React Router v7), and doing that in a broken repo isn't going to make that process any easier. I'll just chalk this up to massive user error, start from the ground up, and be a lot more careful going forward.

Thanks for your time in looking into this.

Gotcha! No worries, sometimes this is the way.

In the future, you could also experiment with changes like this via branches.

Thanks again for your patience! See you around the Community

Hi Pauline,

Sorry for reopening this, but my attempt at starting from scratch is failing in virtually the same way. Here's what I did after completely deleting the entire repo contents (yes, I have a backup):

• Ran npx create-turbo@latest. That built a default Turbo project without any issues.
• Ran npm i to install dependencies. Again, no issues.
• Ran npm install turbo --save-dev. Still no issues.
• Tried to run turbo dev and I get the same error that I reported at the start of this thread, only now it's saying the error is on line 75 instead of 68. I still can't figure out which file it's referring to, as none of the json files I've reviewed have that many lines.

For reference, I'm running NPM v6.14.8, Node 21.7.3, and Turbo 2.4.2

If it'll help, here's the full error log. The error I reported at the start of the thread was just one of many, and I thought that if I could figure out how to fix it, the rest would settle themselves, but perhaps not.

1
turbo 2.4.2
2

3
 WARNING  Issues occurred when constructing package graph. Turbo will function, but some features may not be available:
4
   × Could not resolve workspaces.
5
  ├─▶ Unable to convert from json: missing field `packages` at line 75 column 1
6
  ╰─▶ missing field `packages` at line 75 column 1
7

8
• Packages in scope: @repo/eslint-config, @repo/typescript-config, @repo/ui, docs, web
9
• Running dev in 5 packages
10
• Remote caching disabled
11
┌ web#dev > cache bypass, force executing 4d5346c99fed5ad1 
12
│ 
13
│ > web@0.1.0 dev /Users/justinbarrett/Documents/dev/lightsOverAtlanta/apps/loa-portal/apps/web
14
│ > next dev --turbopack --port 3000
15
│ 
16
│ sh: next: command not found
17
│ npm ERR! code ELIFECYCLE
18
│ npm ERR! syscall spawn
19
│ npm ERR! file sh
20
│ npm ERR! errno ENOENT
21
│ npm ERR! web@0.1.0 dev: `next dev --turbopack --port 3000`
22
│ npm ERR! spawn ENOENT
23
│ npm ERR! 
24
│ npm ERR! Failed at the web@0.1.0 dev script.
25
│ npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
26
│ npm WARN Local package.json exists, but node_modules missing, did you mean to install?
27
│ 
28
│ npm ERR! A complete log of this run can be found in:
29
│ npm ERR!     /Users/justinbarrett/.npm/_logs/2025-02-17T20_26_20_827Z-debug.log
30
└────>
31
┌ docs#dev > cache bypass, force executing 2442233c5da31d2b 
32
│ 
33
│ > docs@0.1.0 dev /Users/justinbarrett/Documents/dev/lightsOverAtlanta/apps/loa-portal/apps/docs
34
│ > next dev --turbopack --port 3001
35
│ 
36
│ sh: next: command not found
37
│ npm ERR! code ELIFECYCLE
38
│ npm ERR! syscall spawn
39
│ npm ERR! file sh
40
│ npm ERR! errno ENOENT
41
│ npm ERR! docs@0.1.0 dev: `next dev --turbopack --port 3001`
42
│ npm ERR! spawn ENOENT
43
│ npm ERR! 
44
│ npm ERR! Failed at the docs@0.1.0 dev script.
45
│ npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
46
│ npm WARN Local package.json exists, but node_modules missing, did you mean to install?
47
│ 
48
│ npm ERR! A complete log of this run can be found in:
49
│ npm ERR!     /Users/justinbarrett/.npm/_logs/2025-02-17T20_26_20_827Z-debug.log
50
│ 
51
│ command finished with error: command (/Users/justinbarrett/Documents/dev/lightsOverAtlanta/apps/loa-portal/apps/docs) /Users/justinbarrett/.nvm/versio
52
│ ns/node/v21.7.3/bin/npm run dev exited (1)
53
└────>
54
docs#dev: command (/Users/justinbarrett/Documents/dev/lightsOverAtlanta/apps/loa-portal/apps/docs) /Users/justinbarrett/.nvm/versions/node/v21.7.3/bin/npm run dev exited (1)
55

56
 Tasks:    0 successful, 2 total
57
Cached:    0 cached, 2 total
58
  Time:    512ms 
59
Failed:    docs#dev
60

61
 ERROR  run failed: command  exited (1)

Any insights you could offer would be greatly appreciated.

On a whim I just tried starting a new example Turbo project in a brand new folder, thinking that maybe my old folder might have something that was messing up the process. Still got the same errors as I last posted above.

Checking the "Support policy" page of the Turbo docs, it says that Turbo supports npm 8+. I could've sworn that 6.14.8 was the version I was running before things blew up. However, digging back into earlier commits of the project repo where this all began, the package.json file in my last good commit lists the "packageManager" as "npm@10.5.2".

I installed npm 10.5.2, then ran npm i in the example project folder. Once that was done, I ran turbo dev and...it worked!

Sorry for all of this mess. Clearly I have a lot to learn when it comes to command line tools.

Hey Justin! I'm really happy you got an answer in the end, thank you for coming back and sharing. Hopefully it helps anyone else that stumbles upon a similar issue