What about single-file version back?

[f0rmat1k]

Specificity of my building don't let me use version with includes. Can you add this version?

[kizu]

Can you elaborate on the specifics of your build process? Multiple files are better maintainable, but I guess I could look into adding a build step to combine everything into one file before publishing to npm.

[f0rmat1k]

I organized enb-like structure:

myblock  
├── myblock.js  
└── myblock.jade  

But it's very tiring to use relative paths and two time block name: (include ../myBlock/myBlock). Therefore i just use include myBlock (like blocks.exec('myBlock')) and use gulp to collect all of them into to .views directory, where they all are siblings. New bemto structure requires to write for it special rules, because my approach breaks its relative paths (/lib directory). It isn't fatal, but requires body movements.