-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using build artifacts as dependency #2732
Comments
I don't have any specific support for that, no. The recommended approach would be to create a third project, like a library, that both apps depended on. |
I think building libraries is totally missing at the moment. We should try to get "ng release" command which npm releases a package that can be consumed easily by others. Or did I miss something?!? |
@BernhardRode that's being tracked in #1692. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Is there any way to use the build artifacts in other angular-cli project?
For example, I created project "A" built it and published. Then I have created project "B" and added A to its dependencies (node_modules).
Currently this is the artifacts of project A:
Lets say that Project A has some components I want to use in project B, how can I do it - is it even possible with the current cli version?
The text was updated successfully, but these errors were encountered: