`UNRESOLVED_IMPORT` warning when importing libs from the same Nx workspace

I have a Nx workspace with 1 app and 6 libs (4 of which were generated using @nxext/stencil):

• MyApp
• MainLib (stencil)
• LibA (stencil)
• LibB (stencil)
• LibC (stencil)
• Utils
• Types

MainLib is dependent on LibA and LibB.

When building MainLib I get this error for both LibA and LibB:

Bundling Warning UNRESOLVED_IMPORT
'@bv0012/lib-a' is imported by
../../../libs/main-lib/src/theme/component-map.ts, but could
not be resolved – treating it as an external dependency

There are no inline errors in component-map.ts and my tsconfig.json paths property looks like this:

"paths": {
      "@bv0012/main-lib": ["libs/main-lib/src/components.d.ts"],
      "@bv0012/main-lib/*": ["libs/main-lib/src/*"],
      "@bv0012/main-lib/loader": ["dist/libs/main-lib/loader"],
      "@bv0012/main-lib/react": [
        "dist/libs/generated/main-lib/react/src/components.ts"
      ],
      "@bv0012/types": ["libs/types/src/index.d.ts"],
      "@bv0012/utils": ["libs/utils/src/index.ts"],
      "@bv0012/lib-a": ["dist/libs/lib-a"],
      "@bv0012/lib-b": ["dist/libs/lib-b"],
      "@bv0012/lib-c": ["dist/libs/lib-c"]
    }

I’m pointing the lib paths to dist/ because they’re publishable.

I feel like this is a node-resolve issue but I haven’t had any success debugging it so far.

[DominikPieper]

@luchsamapparat thanks for your help.

Sorry for the late response, I’m at holidays right now. I’ll take a look at soon as I can

[DominikPieper]

Okay, now I’m back and looked into this. I’ll do some experiments as well. The ugly/fastes solution could be using rollup again to bundle the libs. The @nrwl/web plugin does this, cause you can request the dependency tree und bundle up then. I’ll try some more with the stencil compiler but maybe that’s an workaround