Skip to content
This repository has been archived by the owner on Jan 13, 2018. It is now read-only.

0.7.0

Compare
Choose a tag to compare
@arikon arikon released this 18 Nov 17:08
· 105 commits to support/0.10.x since this release
  • Level scanner no longer fails on symlinks

  • css tech correctly generates classes for modifiers without values (#425)

  • Warning is shown when level does not exists or does not contain .bem directory (#418)

  • Ability to specify multiple elems in elem properties in deps.js files (#401):

    ({
      shouldDeps: { block: 'bla', elem: ['e1', 'e2', 'e3'] }
    })

    is equivalent to:

    ({
      shouldDeps: [
          { block: 'bla', elem: 'e1' },
          { block: 'bla', elem: 'e2' },
          { block: 'bla', elem: 'e3' }
    })
  • Shortcut for specifying tech dependencies of the same block (#413):

    { block: 'b',  tech: 'js', mustDeps: { tech: 'bemhtml' }  }

    is equivalent to:

    { block: 'b',  tech: 'js', mustDeps: { block: 'b', tech: 'bemhtml' }  }
  • build command for bem bench is customizable via bem-bench-build
    script in project's package.json

  • GitLibraryNode specifies git dir explicitly with git commands (#355)

  • Base tech is selected according to child's API_VER. Error is thrown when
    base and child techs have different API_VER (#416)

  • It is possible to write tech module as a function (#363):

    module.exports = function(BEM) {
        return {
            //tech mixin
        };
    }
  • It is possible to write level config as a function (#364):

    module.exports = function(BEM) {
        return {
            //level mixin
        };
    }
  • baseLevelName property can be used in level config to specify simple or
    project level by name (#367)

  • scanner of simple level doesn't ignore dirs like name.tech

  • deps: possibility to declare dependence without explicitly including item (#459):

    {
        block: "some-block",
        mustDeps: [
          {block: "other-block", include: false}
        ]
    }

    In this case, other-block won't be included in bundle with some-block automatically. But, if
    bundle requires both some-block and other-block, other-block will always
    be included before some-block.

  • --no-colors option to disable colors in terminal

  • v1 tech warning shows link to migration instructions

  • q-fs and q-http libraries replaced with q-io

  • underscore library replaced with lodash (#94)

  • benchmarks can be built on multiple bundle levels