I'm late to the party, but I've seen this post have had good traction. In order to answer this for people that might be reading this in the future and want an opinion on this:
You have to try it to see if you like using aliases instead of relative paths in your imports. I particularly like it, but I wouldn't do it for every project. There are two downsides with this approach for me:
You have to configure it. And you need to come up with a convention for your import shortcuts. And you may change your mind along the way about an import shortcut and that'll need refactor. Is a task of -5min, but either way, it takes time.
You loose autocompletion.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This article is incomplete for a dev post. What are the pros and cons of this?
I disagree, the core benefit of using aliases is covered at the beginning.
Maybe the core benefit is explained but what about the main drawback.
Everything has pros and cons
I'm late to the party, but I've seen this post have had good traction. In order to answer this for people that might be reading this in the future and want an opinion on this:
You have to try it to see if you like using aliases instead of relative paths in your imports. I particularly like it, but I wouldn't do it for every project. There are two downsides with this approach for me: