Solving the `../../../` problem.

Is it possible to support importing local modules relative to the root directory (or something along those lines) without ejecting? In other words, go from this:

import bar from '../../../foo/bar';

to this:

import bar from 'foo/bar'; // or '@foo/bar', or '@bar', or what have you

I have done this before with create-react-native-app after ejecting by using the babel-plugin-module-resolver.

This can also be accomplished using Webpack aliases.

[percyhanna]

NODE_PATH doesn’t seem like the right solution, as it’s very sensitive to local environments.

Is there a reason why paths.appSrc isn’t added to resolve as a default source path? That seems like a much better solution that provides absolute paths out of the box, and isn’t fragile based on user environment/configuration.

[Palisand]

@Timer Was this closed because using NODE_PATH, which some would consider confusing or an anti-pattern, is really the only way to accomplish this?