Aleksei Gurianov

Ok. Investigated a bit more. In fact both nodejs require and webpack require works well with windows separators in path. Even with mixed ones like: `require('./components\\App\\App.js')`; The problems starts when...

One more suggestion: https://github.com/Yeti-or/required-path/pull/3#issuecomment-322732678

still waiting an answer from @Yeti-or

https://www.google.com/design/spec/components/buttons-floating-action-button.html

working example for input: ``` js modules.define('angular-bem', ['jquery'], function(provide, $, ngBem) { provide(ngBem.directive('inputAngular', function() { return { restrict : 'C', require : '?ngModel', link : function(scope, element, attrs, ngModel) {...

We can list here bem-components blocks that need such directives. - [x] input - [ ] attach - [ ] checkbox - [ ] checkbox-group - [ ] menu -...

I have an enb tech: ``` js var path = require('path'); module.exports = require('enb/lib/build-flow').create() .name('angular-templates') .useFileList(['tmpl.html']) .target('target', 'templates.html') .justJoinFiles(function (filename, data) { return '\n' + data + '\n'; }) .createTech();...

- This repo doesn't have enb support - Where do you suppose to place code for compiling templates? Library doesn't have app definition ATM. Define as separate block/module?

https://github.com/bem-incubator/enb-ng-techs ``` sh npm install --save-dev enb-ng-techs ```

I was able to fix it in 7.36.2 by adding await to getLatest.prefetch. But I am not sure that it is a proper solution since it gives a different behaviour...