Investigate undiscovered tasks about turbo HOT 5 CLOSED

This bug only seems to be impacting Intel-based macs.

It is possible this is related to a gotcha for PNPM users who specify their workspace packages with double star globs

from turbo.

I just came across the similar problem

And it works with single star.

When using double star globs, it seems all the node_module build script will be executed

from turbo.

Doublestar bug: #32

from turbo.

My current monorepo uses npm and I didn't set up the workspaces, I used to use lerna bootstrap because I was jumping between Node 14 and Node 16. The former is where tap unit test coverage works, but only the latter supports workspaces.

Anyway, until I set up npm workspaces, I was getting 0 cached, 0 total too! Turbo was ending in 100ms. For context, my 120 packages build on Lerna with --concurrency 1 takes around an hour.

Whoever is on npm and getting 0 total, ensure you've got workspaces set up, use engines to enforce Node 16:

// root package.json
+  "workspaces": [
+.   "packages/*"
+  ],
+  "engines": {
+    "node": ">=16.0.0"
+  },

from turbo.

Going to close this but also tie it to #180 and #32

from turbo.