Vladimir Grinenko

http://clubs.ya.ru/bem/replies.xml?parent_id=4035&item_no=3922&with_parent=1#reply-bem-4035

Decide if it should be implemented in main branch after `i18n` support appear in `bem-core v2` or make it as an option in https://github.com/bem/generator-bem-stub

See: http://take.ms/2GHKG Initially reported to https://github.com/bem/project-stub/issues/142

Add possibility to store utility targets in tmp dir

2

We have possibility to define which targets needed for the user and which are just for needs of building process. So it'd great to store utility targets into `.enb/tmp/` folder...

When using ENB via API, it's often very convenient to have a way to pass some data to `make.js` context. E.g. In `prj/custom-script.js` ``` js require('enb').make(targets, options, { a: 1...

At least a notice about it should be added to examples in proper techs. E.g. `file-merge`, https://github.com/enb-bem/enb-xjst/blob/master/techs/html-from-bemjson-i18n.js, etc.

Add support for different file extensions for tech with respect for real order

12

Please refer https://github.com/enb-make/enb-stylus/issues/47 for an example. Idea is to introduce new syntax like `.useFileList('css || styl')` for such cases.

Now it's possible to set up `mode` with the help of environment variable and via JS API. And the only way to use it is declarative: ``` js node.mode('production', function()...