{ "componentChunkName": "component---src-templates-post-js", "path": "/blog/bem-sass-react", "result": {"data":{"markdownRemark":{"html":"

Unless you are using Styled-components for styling ReactJS components, the choice of class naming convention directly affects the productivity and more.

\n

There’s no argue why we should be using some CSS preprocessors instead of plain CSS. Read through 7 benefits of using SASS over conventional CSS to remind yourself of why.\nSASS provides 2 different syntaxes - SASS and SCSS. I prefer SCSS as it is CSS-compatible, meaning that when you rename your CSS file from XYZ.css to XYZ.scss, it immediately becomes a valid SCSS file.

\n

Now, what is BEM?\nBEM, which stands for Block-Element-Modifier, is one of the most well-accepted CSS naming conventions.\nTo give you a quick & easy overview of what BEM looks like:

\n

Block (B)

\n
<div class=\"book\">...</div>\n.book {\n  color: #EFEFEF;\n}
\n

Element (E)

\n
<div class=\"book\">\n  ...\n  <span class=\"book__author\"></span>\n</div>\n.book__author {\n  color: #004345;\n}
\n

Modifier (M)

\n
<div class=\"book book--sold\">...</div>\n.book--sold {\n  text-decoration: stroke;\n}
\n

(reference: BEM — Block Element Modifier)

\n

Besides enabling a global naming rule for your project and the team, BEM provides several other advantages.

\n\n

(reference: To BEM or not to BEM? That is the question.)\nBEM couples well with SCSS syntax. Imagine you write CSS rules for a book element.

\n
<div class=\"book\">\n  <span class=\"book__author\">Napoleon Hill</span>\n  <span class=\"book__title\">Think and Grow Rich</span>\n</div>\n<div class=\"book book--sold\">\n  <span class=\"book__author\">David Schwartz</span>\n  <span class=\"book__title\">The Magic of Thinking Big</span>\n</div>
\n
.book { background-color: black; }\n.book__author { color: white; }\n.book__title { font-weight: bold; color: white; }\n.book--sold { text-decoration: stroke; }
\n

Let’s rewrite this rule in SCSS.

\n
.book {\n  background-color: black;\n  \n  &__author {\n    color: white;\n  }\n  &__title {\n    font-weight: bold;\n    color: white;\n  }\n  \n  &--sold {\n    text-decoration: stroke;\n  }\n}
\n

The nested syntax of SCSS plays a major role in the beauty of BEM blended in SCSS.

\n

With the basic knowledge of SCSS and BEM so far, let’s explore my self-found best practice for writing component styles using them.\nLet us assume that we are working on a project structure like the following:

\n
project\n - src\n   - components\n     - Book.jsx\n     - Book.style.scss\n     - Article.jsx\n     - Article.style.scss\n     - ...\n   - containers\n     - Archive.container.jsx\n     - Archive.style.scss\n     - ...\n   - styles\n   - utils\n - node_modules\n - ...
\n

One of the common misconceptions when writing a component style is ignoring the name conflicts.\nImagine we write styles for Book component and Article component separately.

\n
highlight.js
\n
...\nimport './Book.style.scss';\n...\nexport default ({ author, title }) => (\n  <div className=\"book\">\n    <span className=\"author\">{author}</span>\n    <span className=\"title\">{title}</span>\n    ...\n  </div>\n);
\n
Book.style.scss
\n
.author { color: white; }\n.title { font-weight: bold; color: white; }
\n
Article.jsx
\n
...\nimport './Article.style.scss';\n...\nexport default ({ author, title }) => (\n  <div className=\"article\">\n    <span className=\"author\">{author}</span>\n    <span className=\"title\">{title}</span>\n    ...\n  </div>\n);
\n
Article.style.scss
\n
.author { color: blue; }\n.title { text-decoration: underline; color: blue; }
\n

One could falsely assume that these two styles are kept local to the respective components, but they are not. As and when these two components render on the same page, the unwanted conflicts of CSS rules occur.\nNote the resulting HTML page source:

\n
<body>\n  ...\n  <div class=\"book\">\n    <span class=\"author\">Napoleon Hill</span>\n    <span class=\"title\">Think and Grow Rich</span>\n  </div>\n  ...\n  <div class=\"article\">\n    <span class=\"author\">danny liu</span>\n    <span class=\"title\">BEM and SCSS in ReactJS applications</span>\n  </div>\n  ...\n</body>\n<style>\n  ...\n  .author { color: white; }\n  .title { font-weight: bold; color: white; }\n  ...\n  .author { color: blue; }\n  .title { text-decoration: underline; color: blue; }\n  ...\n</style>
\n

The prettiest solution to the above issue is applying scopes, the unique namespaces, for each component style definitions.

\n
Book.style.scss
\n
.book {\n  .author {\n    color: white;\n  }\n  .title {\n    font-weight: bold;\n    color: white;\n  }\n}
\n
Article.style.scss
\n
.article {\n  .author {\n    color: blue;\n  }\n  .title {\n    text-decoration: underline;\n    color: blue;\n  }\n}
\n

If you chose to use BEM, the namespacing of component styles would come naturally, and you don’t need to stress about remembering it every time. Meanwhile, your application benefits from the aforementioned BEM advantages as well.

\n
Book.style.scss
\n
.book {\n  &__author {\n    color: white;\n  }\n  &__title {\n    font-weight: bold;\n    color: white;\n  }\n}
\n
Article.style.scss
\n
.article {\n  &__author {\n    color: blue;\n  }\n  &__title {\n    text-decoration: underline;\n    color: blue;\n  }\n}
\n

Caution: Stick to the habit of assigning UNIQUE class names to the root DOM elements of your components. Otherwise, the conflicts of CSS rules will happen.

","frontmatter":{"title":"BEM and SASS in ReactJS Applications","description":"Unless you are using Styled-components for","date":"2020-05-19T00:00:00.000Z","slug":"/blog/bem-sass-react","tags":["Blogging","Tech"]}}},"pageContext":{}}, "staticQueryHashes": ["2009693873","2077189868","3303540520","3505212370","3825832676"]}