dependents / dependents/node-filing-cabinet
configure NODE_PATH?
- Dominant language
- JavaScript
- Stars
- 87
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
Hey,
we're using something similar to https://gist.github.com/branneman/8048520#52-only-while-executing-node to prevent having to use long, relative paths when importing/requiring modules.
Is there a way to make filing cabinet aware of such a situation? I'm trying to build a dependency graph for a project that uses `NODE_PATH=src` and would like to be able to resolve something like `import Foo from 'components/Foo'` to `/absolute/path/to/project/src/components/Foo.js`
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files or tests. Start by tracing filing cabinet's module-resolution entry point and existing path-resolution behavior, then verify it with a project using NODE_PATH=src; it is done when imports such as components/Foo resolve to the corresponding file under the configured source path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100