JavaScript HTML Other
Permalink
Failed to load latest commit information.
.enb dist: Remove i-bem-dom__init_auto from no-autoinit bundle (#1482) Feb 20, 2017
.githooks/pre-commit Run linters for PR #1043 Apr 6, 2016
common.blocks Remove old bem-tools remnants Jul 22, 2018
common.bundles/index Remove old bem-tools remnants Jul 22, 2018
common.docs Remove old bem-tools remnants Jul 22, 2018
desktop.blocks Remove old bem-tools remnants Jul 22, 2018
test/dist fix identify Oct 24, 2016
tools Fix jsdoc autoupdater Aug 1, 2014
touch.blocks Remove old bem-tools remnants Jul 22, 2018
.bemrc.js Introduce .bemrc Apr 21, 2018
.bowerrc user bower for dependencies management Feb 3, 2014
.gitignore Added GitBook Apr 28, 2018
.jscs.json Drop xjst base tmpls and i-bem__i18n, update infra Apr 20, 2016
.jshint-groups.js Drop xjst base tmpls and i-bem__i18n, update infra Apr 20, 2016
.jshintrc Add common .jshintrc May 11, 2017
.travis.yml Use container infrastructure to run builds in Travis Apr 6, 2016
CHANGELOG.md Changelog for 4.2.1 Jun 19, 2017
CHANGELOG.ru.md Changelog for 4.2.1 Jun 19, 2017
CLA.md Create CLA.md Apr 21, 2017
CONTRIBUTING.md Update CONTRIBUTING.md Apr 21, 2017
CONTRIBUTING.ru.md Update CONTRIBUTING.ru.md Apr 21, 2017
LICENSE.txt license: Fix typo components -> core May 27, 2015
MIGRATION.md Drop elem cache is broken on init() call Jun 16, 2017
MIGRATION.ru.md Drop elem cache is broken on init() call Jun 16, 2017
README.md Example v2 -> v4 in README.md Apr 4, 2018
README.ru.md Fix url to JSDoc (#1545) Feb 4, 2018
SUMMARY.md Added GitBook Apr 28, 2018
book.json Added GitBook Apr 28, 2018
bower.json bower.json: Remove extra fields Oct 12, 2016
package.json Drop old bem-tools Jul 21, 2018

README.md

bem-core library Build Status GitHub Release devDependency Status

Documentation on bem-core in a much more informative way is also available at bem.info. It is also available in Russian.

What is this?

bem-core is a base library for web interface development. It provides the minimal stack for coding client-side JavaScript and templating.

Use

The easiest way to run a project with bem-core is to use the project-stub.

You can use any other way you are familiar with to include the library into the project.

Inside

Levels

  • common.blocks — suited for any devices and browsers
  • desktop.blocks — should be used for desktop browsers
  • touch.blocks — implement some touch-platforms specifics

Blocks

  • i-bem — base block with helpers for JS and HTML
  • strings — helpers for JS-strings
  • objects — helpers for JS-objects
  • functions — helpers for JS-functions
  • events — JS-events
  • querystring — helpers for work with querystring
  • tick — global timer
  • idle — IDLE event
  • next-tick — polyfill for nextTick/setTimeout(0, ...)
  • inherit — OOP helpers
  • jquery — jQuery
  • clearfix — CSS clearfix trick
  • identify — identify JS-objects
  • cookie — helpers for work with browser cookies
  • vow — Promises/A+ implementation
  • dom — helpers for work with DOM
  • loader — loader for JS files
  • ua — browser features detection
  • keyboard — keyboard helpers
  • page — html/head/body scaffold

Technologies

  • vanilla.js + browser.js
  • bemhtml
  • bemtree

API

The autogenerated JSDoc API can be found on bem.info. E.g. JSDoc for i-bem is here https://en.bem.info/platform/libs/bem-core/current/desktop/i-bem/#jsdoc

Changelog

You can check the changelog at the Changelog page.

Migration

If you used BEM before, check the migration instructions.

Development

Working copy

  1. Get the needed version code (e.g., v4):

    $ git clone -b v4 git://github.com/bem/bem-core.git
    $ cd bem-core
  2. Install the dependencies:

    $ npm install

    You need export PATH=./node_modules/.bin:$PATH or an alternative way to run locally-installed npm dependencies.

  3. Install all necessary libraries:

    $ npm run deps
  4. Build and run tests (specs):

    $ npm test
  5. Run development server:

    $ npm start

How to contribute

Please refer to How to contribute guide.

Modular testing

A default test bundle for functions__debounce:

$ magic make desktop.specs/functions__debounce

You can see the results of the tests in the terminal after the building process finishes.

You can also watch them in a browser loading desktop.specs/functions__debounce/spec-js+browser-js+bemhtml/spec-js+browser-js+bemhtml.html.

Run tests for other BEM entities in the same way. This will work for those which are equipped with .spec.js file.

Code coverage

To build code coverage report add ISTANBUL_COVERAGE=yes environment variable to the tests run command:

$ ISTANBUL_COVERAGE=yes magic make desktop.specs && istanbul report html

You can run modular testing with coverage as well by using more concrete build target as was described above.

$ ISTANBUL_COVERAGE=yes magic make desktop.specs/functions__debounce && istanbul report html

After tests finish, you can view coverage HTML report by opening coverage/index.html in your favorite browser.

The whole code coverage statistics can be found on the bem-core profile page on Coveralls.

Tests are built with a enb-bem-specs library. Check the details (available in Russian only).

Supported browsers

Our browser support policy is based on statistics we get from Yandex services.

Browsers with more than 2% users get full compliant support, more than 0.5% — partially compliant (which means that data is accessible but not necessary 100% functional). New features testing is not provided by us for  browsers with less than 0.5% users.

Desktop

Fully compliant

  • Google Chrome 29+
  • Firefox 24+
  • Yandex 1.7+
  • Opera 12.16
  • MSIE 10.0
  • MSIE 9.0
  • MSIE 8.0
  • Opera 12.15

Partially compliant

  • Opera 17.0
  • Opera 16.0
  • Opera 12.14
  • Opera 12.2
  • Firefox 23

Touch

Fully compliant

  • iOS 6+
  • Android 2.3+
  • Opera Mobile 12+
  • Windows Phone 7+

Partially compliant

  • iOS 5
  • Android 2.2

License

Code and documentation copyright 2012 YANDEX LLC. Code released under the Mozilla Public License 2.0.