You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 1-js/03-code-quality/06-polyfills/article.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,13 +9,13 @@ So it's quite common for an engine to implement only the part of the standard.
9
9
10
10
A good page to see the current state of support for language features is <https://kangax.github.io/compat-table/es6/> (it's big, we have a lot to study yet).
11
11
12
-
## Babel.JS
12
+
## Babel
13
13
14
14
When we use modern features of the language, some engines may fail to support such code. Just as said, not all features are implemented everywhere.
15
15
16
-
Here Babel.JS comes to the rescue.
16
+
Here Babel comes to the rescue.
17
17
18
-
[Babel.JS](https://babeljs.io) is a [transpiler](https://en.wikipedia.org/wiki/Source-to-source_compiler). It rewrites modern JavaScript code into the previous standard.
18
+
[Babel](https://babeljs.io) is a [transpiler](https://en.wikipedia.org/wiki/Source-to-source_compiler). It rewrites modern JavaScript code into the previous standard.
19
19
20
20
Actually, there are two parts in Babel:
21
21
@@ -33,7 +33,7 @@ Actually, there are two parts in Babel:
33
33
34
34
So, we need to setup the transpiler and add the polyfill for old engines to support modern features.
35
35
36
-
If we orient towards modern engines and do not use features except those supported everywhere, then we don't need to use Babel.JS.
36
+
If we orient towards modern engines and do not use features except those supported everywhere, then we don't need to use Babel.
0 commit comments