---
title: "Comment by Grigorii K. Shartsev on \"Why aren't you using Aliases in webpack config?\" | Hashnode"
description: "I don&#39;t use Webpack Aliases. Even common-used like @ for src . I don&#39;t think about import. Moreover, I usually don&#39;t even touch them. How? I&#39;m u"
url: "https://hashnode.com/posts/why-arent-you-using-aliases-in-webpack-config/5de7850aacfca8b73dfaf7eb/comment/5de8291dacfca8b73dfafd7b"
---

[Discussion](https://hashnode.com/posts/why-arent-you-using-aliases-in-webpack-config/5de7850aacfca8b73dfaf7eb)

Comment [Why aren't you using Aliases in webpack config?](https://hashnode.com/posts/why-arent-you-using-aliases-in-webpack-config/5de7850aacfca8b73dfaf7eb)

[Grigorii K. Shartsev](https://hashnode.com/@ShGK_me)

[Dec 4, 2019](https://hashnode.com/posts/why-arent-you-using-aliases-in-webpack-config/5de7850aacfca8b73dfaf7eb/comment/5de8291dacfca8b73dfafd7b)

I don't use Webpack Aliases. Even common-used like `@` for `src`.

1.  I don't think about import. Moreover, I usually don't even touch them. How? I'm using modern IDE. Apps like JetBrains WebStorm, IntellijI IDEA etc have perfect auto-imports.
    
2.  Not all IDE and not always works perfect with aliases. For example, known bug with resolving alias in project from Yarn Workspace: [youtrack.jetbrains.com/issue/WEB-39641](https://youtrack.jetbrains.com/issue/WEB-39641)
    
3.  Agreements. I think, if it's not commonly used alias (like `@` for `src`), the code could be too unobvious, unclear with such aliases... It'd unnecessary agreements.
    
4.  Today it's an application. Tomorrow we want co make a library from a part of code. Won't aliases make our code less reusable?
    

Maybe we just need to make project structure simpler, less deep?
