Andri Möll

Will this fix the problem of passing an object with inherited properties to `extend`? I'm currently getting «No implementation found for exposed method...» for functions that are inherited from another...

Umm, what do you mean by mixin mechanism? I've just got `Object.create` in mind to take advantage of prototypes in a _prototypical_ language. :)

Ah, thx, mkay, then it makes sense inherited properties won't work now. I take it the proposal in this issue will split the inheritance and method-exposing and class registering bits,...

That's possibly not a good idea to do automatically. Given that it's most likely to happen via `at_exit`, it might introduce race conditions if some code, like some test runners...

Aah, got it. And it does get killed as a child at the moment.

Right, stdlib! I propose we could depend merely on `PATH` and let other cases be handled with passing the exe path to `Vimrunner.start`, just like it does today. As long...

Well, it doesn't seem to work. I'm suspecting it might have something to do with this relative check on https://github.com/maxogden/dependency-check/blob/f3f7201d6da262e3b9b0dc131381fba23a42c81b/index.js#L133. ``` javascript if (IS_NOT_RELATIVE.test(req) && !isCore) { ```

Ah, as I read the code further, I'm suspecting that guess was hasty and wrong. :innocent: You know the code better. Is this symlink thing working for you?

You mean you too have a symlink named, e.g., "root" inside node_modules that links to ".." and then require things as `require("root/lib/smth")`?

That's clever too. But, yeah, I was talking about that other pattern, hence the question on how to get that working. :)