Good question.

I had tried this approach and had issues in getting it to work. Particularly, how to specify that jade was still a dependency in package.json. Both regular dependency and peer dependency didn't seem to fit the bill.

A simple proof-of-concept would be to take the built-in binary and have that be it's own package which depends on jade and jade-inheritance.

If you can offer some advice on how to go about this, could you create an issue? https://github.com/paulyoung/jade-inheritance/issues

Thanks!