getElementById ( 'btnBooks' ) let bookList = ītnBooks. This is great news because we can now load JavaScript modules at runtime as in the following example: const baseModulePath = './modules' const btnBooks = document. Also, the module specifier can be any expression returning a string. The statement accepts a module specifier as an argument and returns a promise. The new import ( ) statement solves these issues by allowing you to import modules dynamically. Also, evaluating each dependent module at load time affects the performance of the application. These constraints prevent loading modules conditionally or on-demand.

the specifier of the module ( './my-module.js' in the example above) is a string constant, and you can not change it at runtime.all the code of the imported module is evaluated at the load time of the current module.This statement has a couple of constraints: The current mechanism for importing modules is based on static declarations like the following: import * as MyModule from './my-module.js' But let's go in order and see them in detail. Among these, a feature that developers have been requesting for a long time is the dynamic import. Some important innovations concern modules.

New exciting features are coming for JavaScript!Įven if the final approval of the new ECMAScript 2020 (ES2020) language specification will be in June, you can start to take a look and try them right now!įollow me in this article to explore what's new.

Ecmascript 2020