Two Librarys: internal and external - external should just "bundle inside" some parts of the internal.

[VForsmann]

Heyhey! :)

I hope my question is not too stupid.
We have been using NX for a long time.

In addition to some apps, we also create a library (let's call it A).
The apps can easily access the shared functions of the library.
Even other apps (not included in the monorepo) use the library, which we publish for internal purposes via the AWS registry (password protected).

Now that demand is increasing, we would like to publish a second library that is not password protected.
It will also be published on NPM.

We would like to use parts of Library A and simplify it a bit. I will call this second library B.

If I now have B built (rollup), then the library will also be built successfully.
However, library A is automatically added as a dependency in the bundled library (can see it in the package.json).
I understand that, and it makes sense!
However, A will not be available to the public, and therefore the external installation will not work.

Can I tell NX (or the bundler?!) to bundle the imported parts from Library A directly into Library B?

If so, how?

Thank you!
Vitus

[VForsmann]

Ah - sorry about that.
As I've just realised (while typing), this is probably quite clearly a question for the bundler.
Not for NX.