Indeed. You'd be much better off using webpack (or similar) to set the search paths, and then just require('foo').
It really saves time when you forget what nesting level you are at, and are trying to get to some other folder. I can easily remember my absolute paths, but always forget the amount of "../../.." I need. It's also nice to be able to copy imports from your "src" folder to your "test" folder, and just have them work (which they do when using absolute paths).
This is an interesting take on that idea (using symlinks instead of transpiling).
Can I configure Webpack so that
require("app/foo")
imports `foo` from my project root, even if my project root folder isn't named `app` (it's something like `src`)?I mean, I want a namespace prefix for my stuff, but I don't want to set the search path to ".." or whatever.