Created by: ccorcos
The benefit of using absolute file paths is it's easier to lookup where a file is being used and its easier to move a file using a find-replace-all on the file's path. I like to use absolute paths for all all of my imports.
As discussed here, it would be great if this feature was supported natively by Node.js. For example:
mkdir cool-app
cd cool-app
npm init -y
echo "module.exports = { name: 'chet' }" > defs.js
echo "console.log('hello' + require('cool-app/defs').name)" > index.js
node index.js
> hello chetThe interesting thing is approach is if you publish a Node.js library with this pattern and another project tries to require this package, all the paths would resolve correctly because the project-name now resolved to the node_module!
Anyways, the first commit is the specific feature I'm interested in. And if you feel like this is a good pattern to encourage, the second commit changes the generated templates to use absolute imports.
P.S. some additional discussion here: https://github.com/facebookincubator/create-react-app/issues/636