Alias package name to root directory #651
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
The 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: #636