Rafael Triantafillidis

Can we add a critical label on this issue as it is one of the most requested features?

@aspiers Hi. Is the project still alive? Can you please merge this?

@heloufir @pachoGit Would you be so kind and provide a minimal repro using stackblitz please? I can't make it work.

I'm getting ``` error: invalid package.json name "@orgName/packageName" in { 47, 104, ... }" ``` when running `bun link` `bun -v` -> `1.0.14`

Did some experiments and the reason that above was failing is because my packageName was actually like "@orgName/libs/packageName". Apparently this convention is not allowed by neither bun or npm.

Some updates: I started trying to create a repro and figured out that I had different minor versions of angular in the library and the application(17.3.2 vs 17.0.0). Updating the...

Yep, this fixed it on the stackblitz repro. I still have issues on my main project which is only different from the repro, on that the library is generated in...

For reference: I fixed it, and it was dumb. So i use bun, and i was linking the library with bun link for local testing. Apparently if said library is...

I have the same issue with the latest release.

Who is here after AstralLogs[1] ?