How to properly confine module's dependencies in an angular 6+ library?
I have created an angular library that goes along Angular Package Format guidelines.
I have created several modules inside the library with the purpose of importing only the ones that I want in a specific app. The problem is that if I have module 'A' that needs 'dependency X', when I use some other module of the library in an app, when I run the application and modules are build I get an error saying that the 'dependency X' cannot be found, eventhough I am not importing the module that used the 'dependency X'. This doesn't seem right to me since it doesn't make sense to be forced add a bunch of dependencies that are not of the application itself just because some module of the library, that is not even being used, needs it.
I have been searching the web for some time now to try to find the solution for this but I couldn't find any relevant information.
I messed a lot with the peerDependencies of the package.json since it is pointed here that the lib dependencies should go there (although it seems that the dependencies that should go here are the indispensable ones and not dependencies that are required for one module) and also with lib.externals of the ng-package.json that seems to have been removed in the last versions.
I was not able to solve my problem and I assume it must exist a solution to this problem. So my question is: What is the proper way to manage module's dependencies inside an angular 6+ library?
P.S.: I hope I have been clear enough since it is just written text but if you feel that I should add anything to make this more clear and helpful for others just say and I'll edit it accordingly. Thank you
angular angular-library
asked Nov 19 '18 at 13:41
António QuadradoAntónio Quadrado
7071820
add a comment |
I have created an angular library that goes along Angular Package Format guidelines.
I have created several modules inside the library with the purpose of importing only the ones that I want in a specific app. The problem is that if I have module 'A' that needs 'dependency X', when I use some other module of the library in an app, when I run the application and modules are build I get an error saying that the 'dependency X' cannot be found, eventhough I am not importing the module that used the 'dependency X'. This doesn't seem right to me since it doesn't make sense to be forced add a bunch of dependencies that are not of the application itself just because some module of the library, that is not even being used, needs it.
I have been searching the web for some time now to try to find the solution for this but I couldn't find any relevant information.
I messed a lot with the peerDependencies of the package.json since it is pointed here that the lib dependencies should go there (although it seems that the dependencies that should go here are the indispensable ones and not dependencies that are required for one module) and also with lib.externals of the ng-package.json that seems to have been removed in the last versions.
I was not able to solve my problem and I assume it must exist a solution to this problem. So my question is: What is the proper way to manage module's dependencies inside an angular 6+ library?
P.S.: I hope I have been clear enough since it is just written text but if you feel that I should add anything to make this more clear and helpful for others just say and I'll edit it accordingly. Thank you
angular angular-library
asked Nov 19 '18 at 13:41
António QuadradoAntónio Quadrado
7071820
add a comment |
I have created an angular library that goes along Angular Package Format guidelines.
I have created several modules inside the library with the purpose of importing only the ones that I want in a specific app. The problem is that if I have module 'A' that needs 'dependency X', when I use some other module of the library in an app, when I run the application and modules are build I get an error saying that the 'dependency X' cannot be found, eventhough I am not importing the module that used the 'dependency X'. This doesn't seem right to me since it doesn't make sense to be forced add a bunch of dependencies that are not of the application itself just because some module of the library, that is not even being used, needs it.
I have been searching the web for some time now to try to find the solution for this but I couldn't find any relevant information.
I messed a lot with the peerDependencies of the package.json since it is pointed here that the lib dependencies should go there (although it seems that the dependencies that should go here are the indispensable ones and not dependencies that are required for one module) and also with lib.externals of the ng-package.json that seems to have been removed in the last versions.
I was not able to solve my problem and I assume it must exist a solution to this problem. So my question is: What is the proper way to manage module's dependencies inside an angular 6+ library?
P.S.: I hope I have been clear enough since it is just written text but if you feel that I should add anything to make this more clear and helpful for others just say and I'll edit it accordingly. Thank you
angular angular-library
asked Nov 19 '18 at 13:41
António QuadradoAntónio Quadrado
7071820
I have created an angular library that goes along Angular Package Format guidelines.
I have created several modules inside the library with the purpose of importing only the ones that I want in a specific app. The problem is that if I have module 'A' that needs 'dependency X', when I use some other module of the library in an app, when I run the application and modules are build I get an error saying that the 'dependency X' cannot be found, eventhough I am not importing the module that used the 'dependency X'. This doesn't seem right to me since it doesn't make sense to be forced add a bunch of dependencies that are not of the application itself just because some module of the library, that is not even being used, needs it.
I have been searching the web for some time now to try to find the solution for this but I couldn't find any relevant information.
I messed a lot with the peerDependencies of the package.json since it is pointed here that the lib dependencies should go there (although it seems that the dependencies that should go here are the indispensable ones and not dependencies that are required for one module) and also with lib.externals of the ng-package.json that seems to have been removed in the last versions.
I was not able to solve my problem and I assume it must exist a solution to this problem. So my question is: What is the proper way to manage module's dependencies inside an angular 6+ library?
P.S.: I hope I have been clear enough since it is just written text but if you feel that I should add anything to make this more clear and helpful for others just say and I'll edit it accordingly. Thank you
angular angular-library
angular angular-library
asked Nov 19 '18 at 13:41
António QuadradoAntónio Quadrado
7071820
asked Nov 19 '18 at 13:41
António QuadradoAntónio Quadrado
7071820
edited Nov 19 '18 at 15:36
António Quadrado
asked Nov 19 '18 at 13:41
António QuadradoAntónio Quadrado
7071820
asked Nov 19 '18 at 13:41
António QuadradoAntónio Quadrado
7071820
asked Nov 19 '18 at 13:41
António QuadradoAntónio Quadrado
7071820
7071820
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53375913%2fhow-to-properly-confine-modules-dependencies-in-an-angular-6-library%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53375913%2fhow-to-properly-confine-modules-dependencies-in-an-angular-6-library%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
