ng-packagr: Problem in a multiple library repo: can't inter-depend on each other

Using the programmatic API, we are able to package the libraries in order, and during the packaging we are able to use the already packaged libraries. This packaging process uses a custom tsconfig that looks for the libraries in the place they are packaged to. The order of packaging is very important, as the libs with dependencies must package after the dependecies have finished packaging. Something like:

await ngPackagr()
    .forProject('/usr/local/lib-1/package.json')
    .withTsConfig('tsconfig.packagr.json')
    .build();

await ngPackagr()
    .forProject('/usr/local/lib-2-that-depends-on-lib-1/package.json')
    .withTsConfig('tsconfig.packagr.json')
    .build();

Please check the ngPackagr code for the exact API here: https://github.com/dherges/ng-packagr/blob/v2.4.1/src/lib/ng-v5/packagr.ts

Hi guys is possible avoid the use of link?

i find out a plugin for rollup that could avoid this thing:

https://www.npmjs.com/package/rollup-plugin-paths

but I am not sure if there is a way to include plugin in ng-packagr , someone knows if is something possible?

Thank you! I found that it doesn’t work exactly like that though. I had to do both parts of the linking process. In your nomenclature…

cd packages/lib-a/dist
yarn link
cd ../../..
yarn link lib-a

…which for my repo was solved with the following scripts in the package.json…

    "build:utils": "ng-packagr -p packages/ng-utils/package.json && cd packages/ng-utils && yarn link && cd ../.. && yarn link @animalus/ng-utils",
    "build:date-utils": "ng-packagr -p packages/ng-date-utils/package.json",
    "build": "yarn run build:utils && yarn run build:date-utils"

I also found out the hard way (in that it took me a while to find out why it wasn’t working) that you can’t mix npm link and yarn link commands as they use different global directories to store the links in!

Thanks!

@crowmagnumb you need to use npm link or yarn link. you also need to make sure to package them in the correct order. so for example. in a situation where lib-b depends on lib-a

# Build Package A
ng-packagr -p packages/lib-a 
# Link the output
npm link packages/lib-a/dist
# Now lib-b can reference lib-a and will build correctly
ng-packagr -p packages/lib-b

@mezoistvan awesome that the API opens up the possibility for dependencies for a multi-library repo.

How would this work for Secondary Entry Points, it seems like an overkill to have to suddenly add a full package.json for each entry point. NPM also doesn’t allow the name property to be like @angular/material/button.

Would be great if we can make Secondary Entry Points depend on each other. If there is already a way, would love to know how I could achieve this…

Thanks in advance!

OK, my bad. Sorry. You know how you set up automation, then come to rely on it, and then not really pay attention to it because well it’s all automated right? Well, I just did that. I had automated the linking of the package after building, but then I later moved the location of where the package gets built to but did not update the linking code. So it kept linking to the old place and I didn’t notice. Sorry, this still works. Closing again…