Basically, that's the problem I'm trying to fix. We want it to just work. The JavaScript environment introduced a more tricky situation since we have to fetch the documents over Ajax instead of through a normal IO layer. Certain assumptions about path resolutions had to change and we're gradually ironing them out.

What's important to know is that I view the current status of path and include file resolution as a work in progress and we'll keep hacking on it in core until it works out of the box without the user having to think about base_dir. We'll get there.