Skip to content

Support for alternative paths #500

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
fgarcia opened this issue Aug 23, 2016 · 1 comment
Closed

Support for alternative paths #500

fgarcia opened this issue Aug 23, 2016 · 1 comment

Comments

@fgarcia
Copy link

fgarcia commented Aug 23, 2016

Since myNODE_PATH includes the root of my project folder, many of my imports and requires are not relative. This prevents documentation from finding my code dependencies.

How can I add extra paths to resolve my dependencies?

@tmcw
Copy link
Member

tmcw commented Aug 23, 2016

Hi Francisco,

I think this is the same root issue as #140 - we want to be able to pass custom options into paths so that require() statements don't need to be relative to the current directory. If that's the case, can I close here and we can continue the conversation on that issue?

  • Tom

@fgarcia fgarcia closed this as completed Aug 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants