TBH, if you have that import path issue, that's more a sign that the directory structure you're using is not great. Aliases will solve the import, but navigating that hellish structure will still be bad. Try simplifying your folder structure first, and then you might not need to use aliases at all.
I could use react standard structure. But if I ever move location of a module, then I need to change every occurrence of the import path through my whole project
Not really. If you use a descent editor like VSCode, your imports are updated automatically when you move files. Not to mention that you're just mentioning another issue of having complex directory structures. As I said before, the first step should be to simplify the directory structure. This is not Angular, so we don't need 1000 nesting folders for things to work. Something simple like maybe this...
... should be more than enough. Anything more complex than that is over engineering. In one of your screenshots I see a pattern that you should avoid, which is component folders inside component folders. You should try to keep a flatter structure, by having all components at the same level like the example above. That will reduce duplication, and will force you to code components that are more reusable and less "domain specific".
TBH, if you have that import path issue, that's more a sign that the directory structure you're using is not great. Aliases will solve the import, but navigating that hellish structure will still be bad. Try simplifying your folder structure first, and then you might not need to use aliases at all.
I could use react standard structure. But if I ever move location of a module, then I need to change every occurrence of the import path through my whole project
Not really. If you use a descent editor like VSCode, your imports are updated automatically when you move files. Not to mention that you're just mentioning another issue of having complex directory structures. As I said before, the first step should be to simplify the directory structure. This is not Angular, so we don't need 1000 nesting folders for things to work. Something simple like maybe this...
... should be more than enough. Anything more complex than that is over engineering. In one of your screenshots I see a pattern that you should avoid, which is component folders inside component folders. You should try to keep a flatter structure, by having all components at the same level like the example above. That will reduce duplication, and will force you to code components that are more reusable and less "domain specific".
Thanks, I will look into how to organize my folder tree