This problem is quite common in GitHub's NX repository, but I have not been able to find a solution there.
Within my workspace, I have two buildable libraries: ui/avatar and ui/icon, as well as a publishable library named bar
The goal is to utilize ui/avatar and ui/icon as internal monorepo libraries that can be directly imported into apps. In addition, I want to bundle these buildable libs into bar and publish it as an npm package for external users to benefit from.
Here is an overview of the file structure:
📦libs
┣ 📂external
┃ ┗ 📂bar
┃ ┃ ┣ 📂src
┃ ┃ ...
So far, this initial setup works fine. I can import ui/avatar into bar and generate the @blue/bar package. However, the issue arises with the generated package.json for @blue/bar:
{
"name": "@blue/bar",
"version": "0.0.1",
...
The generated package assumes that ui/avatar is an existing npm package, when in reality I need to include it within the @blue/bar package itself, rather than as an external dependency.
I've attempted to modify the tsconfig.json file of the bar library to locally resolve the dependencies using path mapping (using paths), but so far it has not been successful.
"compilerOptions": {
"declarationMap": false,
"paths": {
"@blue/ui-avatar": ["libs/ui/avatar/src/index.ts"],
"@blue/ui-icon": ["libs/ui/icon/src/index.ts"]
}
}
Any advice or suggestions on how to address this issue would be greatly appreciated. Thank you :)