Best practice for utilizing subpaths in Nx Module libraries

[ksdc-grantw]

Hi Team,

I wanted to get some feedback on utilizing subpaths when importing from other modules. I have a Nx workspace that contains apps and shared libs, including a shared-ui library. As you would imagine, this hold many UI components that are all exported from the root index.ts file.

But the library is growing and I would like to enforce some kind of logical grouping instead of exporting everything from shared-ui. When is library is created, a path is added to tsconfig.base.json, like so:

"paths": {
  "@my-workspace/shared-ui": [ "libs/shared/utils/ui/src/index.ts" ]
}

So I thought, "What if I just add to that?", ie:

"paths": {
  "@my-workspace/shared-ui/forms": [ "libs/shared/utils/ui/src/forms/index.ts" ]
}

This works, things compile and build and run, and the linter is happy. My question is:

• Is this an acceptable way to implement this idea?
• Is there a more acceptable way or more correct way to achieve the same goal?
• Are there things happening in the background or under the hood of Nx that would see this pattern as bad or unuseable?

Im going to go ahead with this for now, I need to move forward. But I look forward to response and discussion.

Thanks,
Grant