Anybody else having problems with deeper path aliases?

[FBosler]

I love the path-aliasing functionality. I am using:

• .babelrc
• jsconfig.json
• visual code

Good news first! All the aliases actually work, i.e. code runs and all is cool. The bad news though. For my deeper (i.e. multi-level) aliases the click-through to the definition or code-peek does not work. Any ideas why?

jsconfig.json
.

{
    "compilerOptions": {
        "baseUrl": ".",
        "paths": {
            "@/TopicOne/*": ["components/Concepts/TopicOne/*"],
            "@/Concepts/*": ["components/Concepts/*"],
            "@/Components/*": ["components/*"]
        }
    },
    "exclude": ["node_modules"]
}

.babelrc

{
    "presets": ["next/babel"],
    "plugins": [
        ["styled-components", { "ssr": true }],
        [
            "module-resolver",
            {
                "root": ["."],
                "alias": {
                    "@/TopicOne": "components/Concepts/TopicOne",
                    "@/Concepts": "components/Concepts",
                    "@/Components": "components"
                }
            }
        ]
    ]
}

[FBosler]

I would really love to get some feedback here. Even if it means to really dig into Webpack or Babel. Some direction would be greatly appreciated!