No, node_modules will be scanned only relative to the current directory going up to the root, so your deeply nested directories won't be searched for as candidates for resolving packages.
You can either install all the dependencies somewhere in the ancestry (e.g. /node_modules) or configure resolve.modules and use absolute imports or you'll have to specify relative paths in the packages in node_modules that will only work on your computer.
These approaches leave you at a disadvantage because it's hard to move your sources between machines, ensure that the correct dependencies are resolved and that they can be kept up-to-date. If you really want modularize your application into "components" that have their own dependencies and can be independently redistributed and maintained from the rest of your sources, then you might want to look into the monorepository pattern.