[New] no-parent-barrel-import: Forbid import from parent barrel file

[jonioni]

Resolves: #2318 (comment)

Forbid import from parent barrel file which often leads to runtime error cannot read ... of undefined.

Gien:

• foo/
  • index.ts
  • bar/
    • index.ts
    • baz.ts
    • qux.ts
  • quux/
    • index.ts
    • ...

// foo/bar/baz.ts
import { T } from '../..';        // forbidden
import { T } from '..';           // forbidden
import { T } from '.';            // forbidden
import { T } from 'foo';          // forbidden
import { T } from 'foo/bar';      // forbidden

import { T } from './qux';        // permitted
import { T } from 'foo/bar/qux';  // permitted
import { U } from '../quux';      // permitted
import { U } from 'foo/quux';     // permitted

It resolves the missing cycle check from no-self-import, while being computationally cheap (over no-cycle)

Rationale

Though it seems that the issue should have been covered by existing rules, there actually isn't one that prevents this circular import / runtime error via parent barrel file (index.js) efficiently.

• no-self-import: doesn't check indirect import
• no-cycle: very costly on large codebase
• no-restricted-paths: requires fixed patterns and not available as a general rule for every folder

Related Issue

There is a related rule of a larger scope: #2408 but further adjustment might be needed. Also it seems to be overly restrictive on importing from non-parent folder (forbids import example2 from '../dir2'; from dir1/file.js) which might need more justification.

[jonioni]

Hi @ljharb, wondering if you could point out why the tests failed with context.report is not a function?