Release helm packages to npmjs

[ppacher]

Hallo!

I'm struggling with an issue for some time now. I have multiple Angular projects (not in the same workspace but scattered across different repositories) where I want to use spartan-ng.

Since I also have a few components that are based on top of spartan-ng (i.e. datepicker, ...) that are shared between all angular projects I want to release this "common" lib to npmjs/github packages.

My question is, how can I add all spartan-ng helm packages to this common package and publish them to npm as well? I don't want to add all helm packages to each angular project and use a published "common" package instead.

This worked so far with dedicated entrypoints for each helm package but I needed to change the import paths for all and in all helm-packages from "@spartan-ng/ui-xxx-helm" to the actual package name used on NPM (i.e. "@myorg/ui/xxx").

This now prevents me from updating the packages regulary because there's a lot of manual work for this.
Are there any plans to publish a "@spartan-ng/helm" package to npmjs like it's done with the new "@spartan-ng/brain" package? Or is there any support in the spartan cli to use a different package name instead and maybe also generate ng-package.json files for each helm package?

Hope my issue is clear, thanks for any advice!

[goetzrobin]

Hey there @ppacher! So far there are no plans to do that. However, if you'd like to work on a PR to the CLI that creates a library for each primitive and/or allows for a custom name to be provided when adding the alias to the tsconfig I am happy to help you get started!