No External Import

Disallows the use of external imports.

• What's the motivation of this lint rule?
  • This rule emits warnings if external modules are imported via URL. "deps.ts" and import maps are exception.
• Why is linted code considered bad?
  • Importing external modules just works fine, but it will take time and effort when you want to upgrade those modules if they are imported in multiple places in your project.
• When should it be used?
  • To avoid it you could use "deps.ts convention" or import maps, where you import all external modules and then re-export them or assign aliases to them.
  • If you'd like to follow the "deps.ts convention" or use import maps.

Invalid:

import { assertEquals } from "https://deno.land/[email protected]/testing/asserts.ts";

Valid:

import { assertEquals } from "./deps.ts";

// deps.ts

export {
  assert,
  assertEquals,
  assertStringIncludes,
} from "https://deno.land/[email protected]/testing/asserts.ts";

you can refer to the explanation of this convention here https://docs.deno.com/runtime/manual/basics/modules/#it-seems-unwieldy-to-import-urls-everywhere