Well, I don't know any specifics on Turborepo (I'm not a contributor or anything like that), but I can imagine that it could work if you update the workspaces property in the root package.json to include your directory as well. Something like;

"workspaces": [
  "apps/*",
  "packages/@my-package/*"
]

Might be that you already tried this of course 😁

I didn't try that, specifically, but I would've thought that packages/* would just include everything automatically.

No that will only include one level deep. You can probably also replace it with packages/**/*.

Hm. I did get something like this to work:

"workspaces": [
  "apps/*",
  "packages/my-package/*",
  "packages/*"
]

Kind of like special treatment for that one folder. I can get it to work without scoping (i.e. yarn install builds it and can deploy a test to Vercel). In the my-package folder there's a package.json that builds the two subpackages in there. The only downside I can see to that is needed to add onto the build command for any new package.

The perfect solution would be to have scoping and then anything added to my-package just gets built.

The workspaces addition has gotten me closer though. Thanks for that. :)

Do you think this would work with npm I switched my packages to have scoped @ names in package.json. Now when I try to install a remote dependency in another package it is looking for my local packages in the npm registry! If I use names with out the scoped part, it works just fine.