Do not use wildcard imports.

// bad
import * as AirbnbStyleGuide from './AirbnbStyleGuide';
// good
import AirbnbStyleGuide from './AirbnbStyleGuide';

10.3 And do not export directly from an import.

Why? Although the one-liner is concise, having one clear way to import and one clear way to export makes things consistent.

// bad
// filename es6.js
export { es6 as default } from './AirbnbStyleGuide';
// good
// filename es6.js
import { es6 } from './AirbnbStyleGuide';
export default es6;

Only import from a path in one place.
eslint: no-duplicate-imports

10.6 In modules with a single export, prefer default export over named export.
eslint:

Why? To encourage more files that only ever export one thing, which is better for readability and maintainability.

// bad
export function foo() {}
// good
export default function foo() {}

10.7 Put all imports above non-import statements.
eslint:

Multiline imports should be indented just like multiline array and object literals.

Why? The curly braces follow the same indentation rules as every other curly brace block in the style guide, as do the trailing commas.

// bad
// good
import {
  longNameA,
  longNameB,
  longNameC,
  longNameD,
  longNameE,
} from 'path';

Disallow Webpack loader syntax in module import statements.
eslint: import/no-webpack-loader-syntax

// bad
import fooSass from 'css!sass!foo.scss';
import barCss from 'style!css!bar.css';
// good