Is it possible to have scoped packages? (i.e. start with @)

[mmJordanO]

In the packages folder, I was able to get something without the @ preceding it working, however when I try to do it with it it comes up as not found.

I have:
/packages/@my-package/config

Within that folder, the package.json defines the name the same way. "@my-package/config"

Lastly, in /packages/config/eslint-preset.js I tried adding the new folder a few ways, but none worked.

Examples:

"packages/@my-package/"
"packages/@my-package/**"
"packages/@my-package/config/"

Am I missing something or can we not do this just yet?

[JeroenReumkens]

@mmJordanO Yes, scoped packages seem possible!
What you need to do is the following:

1. Make sure you update the name of your packages in package.json to contain the scopes (@my-package/...)
2. Don't change anything to the folder names — so @my-package/foo should be in the packages/foo directory
3. Run yarn and yarn dev again. Your packages should work now.

If you also update the config packages, you also only change the names in the package.json. Make sure to replace all the references in other config files to these packages as well (linting, etc).

[JeroenReumkens]

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 😁

[mmJordanO]

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

[JeroenReumkens]

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

[mmJordanO]

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. :)

[bherbruck]

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.