Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support tsconfig paths alias #111

Open
cncolder opened this issue Mar 15, 2020 · 5 comments
Open

Support tsconfig paths alias #111

cncolder opened this issue Mar 15, 2020 · 5 comments

Comments

@cncolder
Copy link

Most frontend project use tsconfig paths. And import scss like this @import '@/style/theme';.

// tsconfig.json
{
    "compilerOptions": {
        "paths": {
            "@/*": ["./src/*"]
        }
    }
}
@abreu-dev
Copy link

jsconfig would be nice too

@Mushr0000m
Copy link

Yes please add the tsconfig !

@avlaguta
Copy link

Please add support for the tsconfig.json path alias.

@ADTC
Copy link

ADTC commented Sep 14, 2023

Is this possible? I can't Ctrl-click / Command-click any aliased imports. VSCode tries to create a new file.

Although I like the other features, I installed this extension to solve this particular annoyance specifically. I'm really bummed that it doesn't.

Apparently Visual Studio Code assumes all @import files are relative by default and doesn't recognize aliases defined in tsconfig or jsconfig even though webpack does and correctly resolves them. I hoped this extension would override VS Code's default behavior and fix this annoyance.

@kevbost
Copy link

kevbost commented Aug 20, 2024

This just explained why @import '@src/styles/constants' is causing intellisense to throw errors on scss module usage. Took a lot of digging to figure that out.

Unfortunately, it doesn't seem like there will ever be a resolution since there hasn't been a commit since 2021.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants