auto import always uses relative (to the current file) module paths in presense of baseUri #21860

Activity

2. zpdDG4gta8XKpMCd commented on Feb 12, 2018

   

   ZpdDG4gta (zpdDG4gta8XKpMCd)

   on Feb 12, 2018

   Author

   More actions

   i am talking about import on completion, because i cannot opt out from completion itself and import just comes with it

   there are a few reasons i don't want ./ and ../ in my module paths:

   • i compile the same code for AMD and CommonJs, and absolute paths are a common ground
   • relative paths are a pain to maintain (move files around)

   so how can i get the import on completion to use absolute paths (relative to baseUri) please?
4. Mohamed Hegazy (mhegazy)

   added

   SuggestionAn idea for TypeScriptAn idea for TypeScript

   on Feb 12, 2018
5. alextreppass commented on May 15, 2018

   

   Alex Treppass (alextreppass)

   on May 15, 2018

   Last edited by alextreppass

   More actions

   Hi Andy (Andrewkraft) (@Andy-MS) - did #20619 allow for imports to use baseUrl paths? I see it's marked as closed via #22236, but I'm not sure whether that added the proposed option

   Thanks
6. mhegazy commented on May 15, 2018

   

   Mohamed Hegazy (mhegazy)

   on May 15, 2018

   Contributor

   More actions

   This should be exposed in VSCode (insiders as of now) under "typescript.preferences.importModuleSpecifier": "non-relative"

   👍React with 👍1Reacted by Gentry Riggen

   🎉React with 🎉12Reacted by Alex Treppass, Mick Dekkers, Arthur, Robin, Leonardo Ramos Duarte, Kirill Alexander Khalitov, Gentry Riggen, Daniel Goudie, lsnch, Edo Rivai and 2 more

   ❤️React with ❤️3Reacted by Gentry Riggen, Iago-lito and Rahul Gupta
7. jabsatz commented on Sep 20, 2018

   

   jabsatz (jabsatz)

   on Sep 20, 2018

   More actions

   This keeps happening even with that option enabled, I read in another issue that the completion uses whichever path is shortest as a string and that you were looking into making that into an option. Any updates on that?
9. jabsatz commented on Sep 20, 2018

   

   jabsatz (jabsatz)

   on Sep 20, 2018

   More actions

   jsconfig.json:

   {
   	"compilerOptions": {
   		"target": "esnext",
   		"allowSyntheticDefaultImports": true,
   		"baseUrl": "./src",
   		"paths": {
   			"*": ["*"]
   		},
   	},
   	"exclude": ["node_modules", "build"]
   }
   

   settings:

   {
   	"typescript.preferences.importModuleSpecifier": "non-relative",
   }
   

   If I'm correct, this should resolve packages non-relatively, and it does, but only sometimes. Say for example my folder structure is somewhat like this:

   src/
   ├── components/
   │   ├── common/
   │   │   └── Dialog.jsx
   │   └── profile/
   │       └── Profile.jsx
   └── utils/
       └── calc.js
   

   If I write Dialog in Profile.jsx, intellisense will suggest auto-import from "../common/Dialog", however, if I try to write calc, instead of suggesting "../../utils/calc" it just suggests "utils/calc" (as I expect).
11. jabsatz commented on Sep 20, 2018

    

    jabsatz (jabsatz)

    on Sep 20, 2018

    More actions

    No, should I?
13. jabsatz commented on Sep 21, 2018

    

    jabsatz (jabsatz)

    on Sep 21, 2018

    More actions

    That did the trick! Thank you!
14. Wesley Wigham (weswigham)

    added

    Awaiting More FeedbackThis means we'd like to hear from more people who would be helped by this featureThis means we'd like to hear from more people who would be helped by this feature

    on Nov 6, 2018