Module resolves differently in spec file vs component file
I have a weird issue going on with how my modules are being resolved in a component.ts file versus an adjacent spec.ts file I have for that component.
So consider the following path entry I have in my tsconfig.json situated at the root of my project folder:
"@acme/core": [ "../acme/src" ]
As can be seen, this mapping is to a local version of my acme module I already have on disk.
So in a component ts file where I use a service exported from this module I have
import { MyService } from '@acme/core'
And when I hover over the module reference in my IDE (VS Code) it shows its being correctly picked up from my local acme project on disk.
However when I try doing the same for a spec.ts file where I import my service in the same way, it references it from my node_modules folder where its installed by default from an npm install (from a private repo)
Im wondering why the spec.ts file is not resolving the module in the same way from the root level tsconfig.json file.
I want my spec file to resolve my local project module so I can test some local changes I am making, the same as I am doing in my component ts file.
What could be going wrong here?
Thanks
angular typescript
asked Nov 20 '18 at 16:41
mindparsemindparse
3,57992973
add a comment |
I have a weird issue going on with how my modules are being resolved in a component.ts file versus an adjacent spec.ts file I have for that component.
So consider the following path entry I have in my tsconfig.json situated at the root of my project folder:
"@acme/core": [ "../acme/src" ]
As can be seen, this mapping is to a local version of my acme module I already have on disk.
So in a component ts file where I use a service exported from this module I have
import { MyService } from '@acme/core'
And when I hover over the module reference in my IDE (VS Code) it shows its being correctly picked up from my local acme project on disk.
However when I try doing the same for a spec.ts file where I import my service in the same way, it references it from my node_modules folder where its installed by default from an npm install (from a private repo)
Im wondering why the spec.ts file is not resolving the module in the same way from the root level tsconfig.json file.
I want my spec file to resolve my local project module so I can test some local changes I am making, the same as I am doing in my component ts file.
What could be going wrong here?
Thanks
angular typescript
asked Nov 20 '18 at 16:41
mindparsemindparse
3,57992973
add a comment |
I have a weird issue going on with how my modules are being resolved in a component.ts file versus an adjacent spec.ts file I have for that component.
So consider the following path entry I have in my tsconfig.json situated at the root of my project folder:
"@acme/core": [ "../acme/src" ]
As can be seen, this mapping is to a local version of my acme module I already have on disk.
So in a component ts file where I use a service exported from this module I have
import { MyService } from '@acme/core'
And when I hover over the module reference in my IDE (VS Code) it shows its being correctly picked up from my local acme project on disk.
However when I try doing the same for a spec.ts file where I import my service in the same way, it references it from my node_modules folder where its installed by default from an npm install (from a private repo)
Im wondering why the spec.ts file is not resolving the module in the same way from the root level tsconfig.json file.
I want my spec file to resolve my local project module so I can test some local changes I am making, the same as I am doing in my component ts file.
What could be going wrong here?
Thanks
angular typescript
asked Nov 20 '18 at 16:41
mindparsemindparse
3,57992973
I have a weird issue going on with how my modules are being resolved in a component.ts file versus an adjacent spec.ts file I have for that component.
So consider the following path entry I have in my tsconfig.json situated at the root of my project folder:
"@acme/core": [ "../acme/src" ]
As can be seen, this mapping is to a local version of my acme module I already have on disk.
So in a component ts file where I use a service exported from this module I have
import { MyService } from '@acme/core'
And when I hover over the module reference in my IDE (VS Code) it shows its being correctly picked up from my local acme project on disk.
However when I try doing the same for a spec.ts file where I import my service in the same way, it references it from my node_modules folder where its installed by default from an npm install (from a private repo)
Im wondering why the spec.ts file is not resolving the module in the same way from the root level tsconfig.json file.
I want my spec file to resolve my local project module so I can test some local changes I am making, the same as I am doing in my component ts file.
What could be going wrong here?
Thanks
angular typescript
angular typescript
asked Nov 20 '18 at 16:41
mindparsemindparse
3,57992973
asked Nov 20 '18 at 16:41
mindparsemindparse
3,57992973
asked Nov 20 '18 at 16:41
mindparsemindparse
3,57992973
asked Nov 20 '18 at 16:41
mindparsemindparse
3,57992973
asked Nov 20 '18 at 16:41
mindparsemindparse
3,57992973
3,57992973
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%2f53397608%2fmodule-resolves-differently-in-spec-file-vs-component-file%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%2f53397608%2fmodule-resolves-differently-in-spec-file-vs-component-file%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
