Show library typing/runtime dependencies differently in dependency graph

Expected Behavior

When importing just the type information from a library using Typescript >3.8:

import type { MyInterface } from '@project/my-models';

The affected:dep-graph should indicate it is a type dependency rather than a runtime dependency, or optionally filter type dependencies.

Current Behavior

Libraries which are depended on for just type information are shown with the same dependency arrow-line as those libraries which provide runtime services.

Steps to Reproduce

1. Create an app
2. Create a library
3. Create a interface model in the library and export it.
4. Import the interface via import type into the app.
5. Run affected:dep-graph command.
6. Library is shown as a hard dependency for the app.

Context

  @nrwl/angular : 9.1.4
  @nrwl/cli : 9.1.4
  @nrwl/cypress : 9.1.4
  @nrwl/eslint-plugin-nx : Not Found
  @nrwl/express : Not Found
  @nrwl/jest : 9.1.4
  @nrwl/linter : 9.1.4
  @nrwl/nest : 9.1.4
  @nrwl/next : Not Found
  @nrwl/node : 9.1.4
  @nrwl/react : Not Found
  @nrwl/schematics : Not Found
  @nrwl/tao : 9.1.4
  @nrwl/web : 9.1.4
  @nrwl/workspace : 9.1.4
  typescript : 3.8.3

[spaceribs]

Yeah, i’m a bit confused myself, did this not mean to be released?

[MaximSagan]

Unstale

I might see if I can take this one