Dependency tree analysis

[SteelAlloy]

@divy-work I've moved some files around, tell me how you want to structure the project between Deno's only files, those for the web and the rest.

So I propose the possibility to build a dependency tree and to analyze its imports.

function dependencyTree(path: string, options: TreeOptions): Promise<IDependencyTree>

//Where :
export type DependencyTree = Array<{
  path: string;
  imports: DependencyTree;
}>;

export interface IDependencyTree {
  tree: DependencyTree; // The actual tree
  circular: boolean; // Are there circular imports?
  count: number; // The number of imported files, by removing duplicate entries
  iterator: IterableIterator<string>; // An iterable dependency iterator to, for example, detect whether the tree contains broken dependencies. 
}

export interface TreeOptions {
  fullTree: boolean; // By default, redundant imports are ignored, i.e. they are already elsewhere in the tree and are not duplicated
}

Currently, it only works for Deno but there is almost nothing to change to make it work on the web, tell me how to make it clean without duplicate functions.

/* Resolves any path, relative or HTTP url. */
export function resolveURL(path: string, base = "") {
  if (path.match(/^https?:\/\//)) {
    return path;
  }
  if (base.match(/^https?:\/\//)) {
    return new URL(path, base).href;
  }
 - return fileURL(path, base);
}

/* Fetch data from file: or https: urls */
async function fetchData(url: string) {
-  if (url.match(/^https?:\/\//)) {
    const data = await fetch(url);
    return data.text();
-  }
-  const data = await Deno.readFile(resolve(fromFileUrl(url)));
-  return decoder.decode(data);
}

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nestdotland/analyzer/ekecumnzs
✅ Preview: https://analyzer-git-feat-dependency-tree.nestdotland.vercel.app

[littledivy]

Yay