Angular multi-project workspace dependencies restrictions
up vote
0
down vote
favorite
Node / npm / Angular newbie here.
I have an Angular (v7) workspace with the following structure:
my-workspace
package.json
projects
my-app1: "ng generate application my-app1"
No package.json is generated.
my-app2: "ng generate application my-app2"
No package.json is generated.
my-libA: "ng generate library my-libA"
package.json
my-libB: "ng generate library my-libB"
package.json
my-libC: "ng generate library my-libC"
package.json
my-app1 uses @angular/core, @angular/common, @angular/forms etc.
my-libB only uses @angular/core.
However, I can access @angular/forms from my-libB project.
It should be noted that my-libB/package.json contains only one peerDependencies (@angular/core).
Is there any way I can prevent this improper access so that VS Code / angular-cli might show me a compile error?
angular angular-cli angular-cli-v7
add a comment |
up vote
0
down vote
favorite
Node / npm / Angular newbie here.
I have an Angular (v7) workspace with the following structure:
my-workspace
package.json
projects
my-app1: "ng generate application my-app1"
No package.json is generated.
my-app2: "ng generate application my-app2"
No package.json is generated.
my-libA: "ng generate library my-libA"
package.json
my-libB: "ng generate library my-libB"
package.json
my-libC: "ng generate library my-libC"
package.json
my-app1 uses @angular/core, @angular/common, @angular/forms etc.
my-libB only uses @angular/core.
However, I can access @angular/forms from my-libB project.
It should be noted that my-libB/package.json contains only one peerDependencies (@angular/core).
Is there any way I can prevent this improper access so that VS Code / angular-cli might show me a compile error?
angular angular-cli angular-cli-v7
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Node / npm / Angular newbie here.
I have an Angular (v7) workspace with the following structure:
my-workspace
package.json
projects
my-app1: "ng generate application my-app1"
No package.json is generated.
my-app2: "ng generate application my-app2"
No package.json is generated.
my-libA: "ng generate library my-libA"
package.json
my-libB: "ng generate library my-libB"
package.json
my-libC: "ng generate library my-libC"
package.json
my-app1 uses @angular/core, @angular/common, @angular/forms etc.
my-libB only uses @angular/core.
However, I can access @angular/forms from my-libB project.
It should be noted that my-libB/package.json contains only one peerDependencies (@angular/core).
Is there any way I can prevent this improper access so that VS Code / angular-cli might show me a compile error?
angular angular-cli angular-cli-v7
Node / npm / Angular newbie here.
I have an Angular (v7) workspace with the following structure:
my-workspace
package.json
projects
my-app1: "ng generate application my-app1"
No package.json is generated.
my-app2: "ng generate application my-app2"
No package.json is generated.
my-libA: "ng generate library my-libA"
package.json
my-libB: "ng generate library my-libB"
package.json
my-libC: "ng generate library my-libC"
package.json
my-app1 uses @angular/core, @angular/common, @angular/forms etc.
my-libB only uses @angular/core.
However, I can access @angular/forms from my-libB project.
It should be noted that my-libB/package.json contains only one peerDependencies (@angular/core).
Is there any way I can prevent this improper access so that VS Code / angular-cli might show me a compile error?
angular angular-cli angular-cli-v7
angular angular-cli angular-cli-v7
asked Nov 22 at 15:20
Marlon Patrick
827917
827917
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53434011%2fangular-multi-project-workspace-dependencies-restrictions%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