René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"tsconfig paths and module resolution errors in VS Code","articleBody":"\u003c!--\r\nIF YOU DON'T FILL OUT THE FOLLOWING INFORMATION YOUR ISSUE MIGHT BE CLOSED WITHOUT INVESTIGATING\r\n--\u003e\r\n### Bug Report or Feature Request (mark with an `x`)\r\n```\r\n- [x] bug report -\u003e please search issues before submitting\r\n- [ ] feature request\r\n```\r\n\r\n### Versions.\r\n\u003c!--\r\nOutput from: `ng --version`.\r\nIf nothing, output from: `node --version` and `npm --version`.\r\n  Windows (7/8/10). Linux (incl. distribution). macOS (El Capitan? Sierra?)\r\n--\u003e\r\n\r\n\u003e @angular/cli: 1.4.9\r\nnode: 7.9.0\r\nos: darwin x64\r\n@angular/animations: 4.4.5\r\n@angular/common: 4.4.5\r\n@angular/compiler: 4.4.5\r\n@angular/core: 4.4.5\r\n@angular/forms: 4.4.5\r\n@angular/http: 4.4.5\r\n@angular/platform-browser: 4.4.5\r\n@angular/platform-browser-dynamic: 4.4.5\r\n@angular/router: 4.4.5\r\n@angular/cli: 1.4.9\r\n@angular/compiler-cli: 4.4.5\r\ntypescript: 2.3.4\r\n\r\nmacOS Sierra 10.12.6\r\nVS Code 1.17.2\r\n### Repro steps.\r\n\u003c!--\r\nSimple steps to reproduce this bug.\r\nPlease include: commands run, packages added, related code changes.\r\nA link to a sample repo would help too.\r\n--\u003e\r\nMy tsconfig path property seems broken.\r\nWhen I replace my path mapped imports (@shared, @assets etc.) with the equivalent coded relative paths, typescript module resolution seems to work (vs code intellisense is happy)\r\nI have a large angular 2 project and am used to aliasing my asset and shared directories this way.\r\nNOTE: project builds and (seems) to run just fine\r\nThis has been reported often, but I can't make sense of the current state of this issue.\r\nThis more than annoying as VS Code reports Angular spurious errors on all of my components.\r\nI also suspect this is why I get the infamous Can't read property isSkipSelf of null when I open my templates (html) in VS Code.\r\nI was running 1.4.2 and just tried ~1.4.2, which resolves to 1.4.9 in my package.json, to no avail.\r\nWill 1.5.x fix this?\r\nHow can I help debug this without providing a copy of my app?\r\n\r\nThanks in advance. Regards.\r\n\r\n### The log given by the failure.\r\n\u003c!-- Normally this include a stack trace and some more information. --\u003e\r\n\r\n\r\n### Desired functionality.\r\n\u003c!--\r\nWhat would like to see implemented?\r\nWhat is the usecase?\r\n--\u003e\r\n\r\n\r\n### Mention any other details that might be useful.\r\n\u003c!-- Please include a link to the repo if this is related to an OSS project. --\u003e\r\n\r\n","author":{"url":"https://github.com/SpiraMira","@type":"Person","name":"SpiraMira"},"datePublished":"2017-10-21T08:10:59.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":42},"url":"https://github.com/8138/angular-cli/issues/8138"}