The import statement is used to import members (functions, objects or primitives) that have been exported from an external module. Using a specific member syntax:

// single - Import single member.
import myMember from "my-module.js";

// multiple - Import multiple members.
import {foo, bar} from "my-module.js";

// all - Import all members, where myModule contains all the exported bindings.
import * as myModule from "my-module.js";

The import statement can also import a module without exported bindings. Used when the module does not export anything, but runs it own code or changes the global context object.

// none - Import module without exported bindings.
import "my-module.js"

When declaring multiple imports, a sorted list of import declarations make it easier for developers to read the code and find necessary imports later. This rule is purely a matter of style.

Bad Practice

import b from 'foo.js';
import a from 'bar.js';

import a from 'foo.js';
import A from 'bar.js';

import {b, c} from 'foo.js';
import {a, b} from 'bar.js';

import a from 'foo.js';
import {b, c} from 'bar.js';

import a from 'foo.js';
import * as b from 'bar.js';

import {b, a, c} from 'foo.js'

Recommended

import 'module-without-export.js';
import * as bar from 'bar.js';
import * as foo from 'foo.js';
import {alpha, beta} from 'alpha.js';
import {delta, gamma} from 'delta.js';
import a from 'baz.js';
import b from 'qux.js';

import a from 'foo.js';
import b from 'bar.js';
import c from 'baz.js';

import 'foo.js'
import * as bar from 'bar.js';
import {a, b} from 'baz.js';
import c from 'qux.js';

import {a, b, c} from 'foo.js'