Requiring relative to subtype about enhanced-require

[sokra]

Currently I cannot imagine a solution which is pretty.

But I'll have an idea, that it'll need some minor changes in webpack.

in SpecificViewX.js

var JadeView = require("./JadeView?" + __dirname);

in JadeView.js

var template = require(__resourceQuery + "/template/" + this.name + ".jade");

The change would be to evaluate __dirname and __resourceQuery as compile time constant.

A problem would be that the code of JadeView.js would be duplicated for each directory with SpecificViews.

[miffels]

Interesting, I also had that idea of evaluating __dirname and the like at compile time, but thought that would be too much of a hassle for even mentioning. Plus, you're right, even then I'd have to have a JadeView (or at least a subtype of it with that specific template loading part) in each of my project view root directories since it's still relative to that directory. I guess it's best, in that case, to let each SpecificView load the template on its own, i.e. just duplicate that template loading part. When I am going to move the JadeView type out of my projects in a separate package, then relative path snippets won't do anymore, unfortunately, since you never know where the files would be. On the other hand, I could barely still call it JadeView when it doesn't take care of the template loading, couldn't I :)

Thanks for your suggestions, though! Maybe I'll think about that some more later and let you know, if I have some major enlightenment.

Edit: Having a second look at the JadeView stub, would it really need to be replicated? if __resourceQuery contained the absolute directory path, then it should be just fine.

[sokra]

I made the changes to webpack... webpack/webpack@2183f05

Now here is my idea: https://github.com/sokra/resourceQuery-example

[miffels]

Horrific! I can't wait to give it a try. Thanks a lot!