Hello folks! I have some configuration issues while using multiple projects and I was wondering if you could help. Say I have a project with the following structure

root
├── package-a/
│   ├── package.json
│   ├── tsconfig.json
│
├── package-b/
    ├── package.json
    ├── tsconfig.json

And package-a references package-b in the following way package-a/package.json

{
  "dependencies": {
    "@company/package-b": 1.0.0,
  }
}

package-a/tsconfig.json

{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@company/package-a/*": [
        "src/*"
      ],
      "@company/package-b/*": [
        "../package-b/src/*"
      ]
    }
  }
}

We're doing this to avoid repackaging and reinstalling package-b every time while developing, but we now noticed that while running

sst start

,

package-b

gets added automatically to

externalModules

and hence not bundled when in reality we want it to be bundled. Any suggestions on how to work around this or make it better? Thanks!

I'm making a change to be released this week that will fix this

thanks for the quick response @thdxr 🙇

I'm aiming for end of this week

yeah, while running on dev we're getting errors at runtime because the missing modules. Prod works fine

Do you absolutely need to have separate packages? You can get most of the benefit without making them seperate

not an absolute need, but a big plus for maintenance and separation of concerns if we would get it to work

You can still get that if you just remove the package.json and the npm dependency since the ts path will keep things seperate