-
Notifications
You must be signed in to change notification settings - Fork 165
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
Add an option to specify the "root" directory #171
Comments
Can I assume that you're using this as a required module and not from the command line? |
@remy Correct. Right now I use this wrapper
Which is then used as such
I'm sending in the Maybe there's a better way to do this and avoid the trouble, I wasn't able to find one. |
No, it's fine, it's more that the |
@remy Actually this is not a solution. Because while the promise is "being resolved" another thing can get executed (say another inline request) and it can change the directory before actual inliner code will run then it will have wrong context. Or am I misunderstanding your request? I don't know where and how the paths would need to be modified to take into account some "root" directory. |
How about if you can script a simple test that replicates the problem, and I'll take a look. I think the |
Resolution of relative paths does not seem to work properly, I have to run the node process (or change with
process.chdir
) in the directory where the template is and the paths are resolved properly by node relative to it.It would be nice to be able to specify the root directory so that I can run node in different directory and have assets and template in a different one.
This should probably not "just call
chdir
" becuase that affects all the other code running in the same process as well which might not be wanted.The text was updated successfully, but these errors were encountered: