Angular - Add local external Module to App
I have a project my-components and a project my-showcase. my-components is an Angular library and my-showcase is an Angular app. At time, when I change or add an component in library, I make a commit to private git and publish to private npm. Then I can use it in other apps like my-showcase. Before commit and publish I would test it. Until now, I create and develop a new component in my-showcase. After finish, I put it to my-components.
At time I import my angular component library over npm:
import {TimePickerModule} from '@company/components';
For testing and development I change this to local path:
import {TimePickerModule} from '../../../../company-components/projects/components/src';
Unfortunately, I get the following error message:
WARNING in ../company-components/node_modules/@angular/core/fesm5/core.js 15153:15-36
Critical dependency: the request of a dependency is an expression
And:
core.js:12584 ERROR Error: Uncaught (in promise): Error: StaticInjectorError(AppModule)[DcStickyBitsDirective -> ElementRef]:
StaticInjectorError(Platform: core)[DcStickyBitsDirective -> ElementRef]:
NullInjectorError: No provider for ElementRef!
Apparently the component from the library in app my-showcase use the wrong node_module folder from my-components (specially @angular/core), not the node_module folder from my-showcase.
Does anyone have a solution for me or have I a wrong understanding when dealing with Angular Library and NPM? If it was too incomprehensible, please let me know.
angular typescript npm angular-library
add a comment |
I have a project my-components and a project my-showcase. my-components is an Angular library and my-showcase is an Angular app. At time, when I change or add an component in library, I make a commit to private git and publish to private npm. Then I can use it in other apps like my-showcase. Before commit and publish I would test it. Until now, I create and develop a new component in my-showcase. After finish, I put it to my-components.
At time I import my angular component library over npm:
import {TimePickerModule} from '@company/components';
For testing and development I change this to local path:
import {TimePickerModule} from '../../../../company-components/projects/components/src';
Unfortunately, I get the following error message:
WARNING in ../company-components/node_modules/@angular/core/fesm5/core.js 15153:15-36
Critical dependency: the request of a dependency is an expression
And:
core.js:12584 ERROR Error: Uncaught (in promise): Error: StaticInjectorError(AppModule)[DcStickyBitsDirective -> ElementRef]:
StaticInjectorError(Platform: core)[DcStickyBitsDirective -> ElementRef]:
NullInjectorError: No provider for ElementRef!
Apparently the component from the library in app my-showcase use the wrong node_module folder from my-components (specially @angular/core), not the node_module folder from my-showcase.
Does anyone have a solution for me or have I a wrong understanding when dealing with Angular Library and NPM? If it was too incomprehensible, please let me know.
angular typescript npm angular-library
add a comment |
I have a project my-components and a project my-showcase. my-components is an Angular library and my-showcase is an Angular app. At time, when I change or add an component in library, I make a commit to private git and publish to private npm. Then I can use it in other apps like my-showcase. Before commit and publish I would test it. Until now, I create and develop a new component in my-showcase. After finish, I put it to my-components.
At time I import my angular component library over npm:
import {TimePickerModule} from '@company/components';
For testing and development I change this to local path:
import {TimePickerModule} from '../../../../company-components/projects/components/src';
Unfortunately, I get the following error message:
WARNING in ../company-components/node_modules/@angular/core/fesm5/core.js 15153:15-36
Critical dependency: the request of a dependency is an expression
And:
core.js:12584 ERROR Error: Uncaught (in promise): Error: StaticInjectorError(AppModule)[DcStickyBitsDirective -> ElementRef]:
StaticInjectorError(Platform: core)[DcStickyBitsDirective -> ElementRef]:
NullInjectorError: No provider for ElementRef!
Apparently the component from the library in app my-showcase use the wrong node_module folder from my-components (specially @angular/core), not the node_module folder from my-showcase.
Does anyone have a solution for me or have I a wrong understanding when dealing with Angular Library and NPM? If it was too incomprehensible, please let me know.
angular typescript npm angular-library
I have a project my-components and a project my-showcase. my-components is an Angular library and my-showcase is an Angular app. At time, when I change or add an component in library, I make a commit to private git and publish to private npm. Then I can use it in other apps like my-showcase. Before commit and publish I would test it. Until now, I create and develop a new component in my-showcase. After finish, I put it to my-components.
At time I import my angular component library over npm:
import {TimePickerModule} from '@company/components';
For testing and development I change this to local path:
import {TimePickerModule} from '../../../../company-components/projects/components/src';
Unfortunately, I get the following error message:
WARNING in ../company-components/node_modules/@angular/core/fesm5/core.js 15153:15-36
Critical dependency: the request of a dependency is an expression
And:
core.js:12584 ERROR Error: Uncaught (in promise): Error: StaticInjectorError(AppModule)[DcStickyBitsDirective -> ElementRef]:
StaticInjectorError(Platform: core)[DcStickyBitsDirective -> ElementRef]:
NullInjectorError: No provider for ElementRef!
Apparently the component from the library in app my-showcase use the wrong node_module folder from my-components (specially @angular/core), not the node_module folder from my-showcase.
Does anyone have a solution for me or have I a wrong understanding when dealing with Angular Library and NPM? If it was too incomprehensible, please let me know.
angular typescript npm angular-library
angular typescript npm angular-library
edited Nov 13 '18 at 14:20
William
asked Nov 13 '18 at 14:03
WilliamWilliam
316
316
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I have a workaround. I add following to tsconfig.json:
"@company/components": [
"../path/to/projects/components/src"
],
"@angular/*": [
"node_modules/@angular/*"
]
But I don't find this solution very clean. If I understand correctly, the problem is that Webpack takes the Angular stuff from the component library and not from the showcase project. With this workaround, it override the wrong paths.
add a comment |
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%2f53282748%2fangular-add-local-external-module-to-app%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have a workaround. I add following to tsconfig.json:
"@company/components": [
"../path/to/projects/components/src"
],
"@angular/*": [
"node_modules/@angular/*"
]
But I don't find this solution very clean. If I understand correctly, the problem is that Webpack takes the Angular stuff from the component library and not from the showcase project. With this workaround, it override the wrong paths.
add a comment |
I have a workaround. I add following to tsconfig.json:
"@company/components": [
"../path/to/projects/components/src"
],
"@angular/*": [
"node_modules/@angular/*"
]
But I don't find this solution very clean. If I understand correctly, the problem is that Webpack takes the Angular stuff from the component library and not from the showcase project. With this workaround, it override the wrong paths.
add a comment |
I have a workaround. I add following to tsconfig.json:
"@company/components": [
"../path/to/projects/components/src"
],
"@angular/*": [
"node_modules/@angular/*"
]
But I don't find this solution very clean. If I understand correctly, the problem is that Webpack takes the Angular stuff from the component library and not from the showcase project. With this workaround, it override the wrong paths.
I have a workaround. I add following to tsconfig.json:
"@company/components": [
"../path/to/projects/components/src"
],
"@angular/*": [
"node_modules/@angular/*"
]
But I don't find this solution very clean. If I understand correctly, the problem is that Webpack takes the Angular stuff from the component library and not from the showcase project. With this workaround, it override the wrong paths.
answered Nov 19 '18 at 16:19
WilliamWilliam
316
316
add a comment |
add a comment |
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%2f53282748%2fangular-add-local-external-module-to-app%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