Sergey Berezhnoy

Possibility to write *.spec.js in separate files

1

Right now https://github.com/bem/bem-core/blob/v3/common.blocks/i-bem-dom/i-bem-dom.spec.js is about 1.5K lines and still counting. So we definitely need a way to make something like that: ``` common.blocks/i-bem-dom/i-bem-dom.spec.js/

We need to highlight that our DOM events are implemented throughout jQuery events, so they have all stuff from http://api.jquery.com/on/#event-handler (like `event.stopPropagation()`, `event.preventDefault()`, returning `false` and so on).

Think about it.

Think about simplifying deps format

13

Suggestions: 1. drop `noDeps` 2. get rid of `shouldDeps` in favour of only `mustDeps` semantic

Since #1109 we have a lot of options for promises.

i-bem-dom__event-manager_type_dom: Optimize all "closest" to a single traversing

1

We can avoid many `.closest` calls in favour of custom traversing. Should be done with "benchmark first" strategy. See also https://github.com/bem/bem-core/tree/i-bem-bench%40v2

We need this for progressive initialisation of some blocks before we get declarations for others. cc @dfilatov @narqo @faraser @olliva

i-bem__dom.js: Reference to `body` in static field

1

As we have reference for `document` and `window`, we need reference to `body` in `BEM.DOM`.

Catch EEXIST errors on create directories

1

There is a code in `lib/freeze.js`:" ``` js if (!FS.existsSync(_path)) { FS.mkdirSync(_path); } ``` it's does't work properly because it's possible to catch state when `FS.existsSync` passed, but before `FS.mkdirSync`...

Command for recursive processing all files in directories with specified beautifiers and with filtering through `.krasotaignore` files. Feature branch: https://github.com/veged/krasota.js/tree/recursive