Using own package name in import statement causes missing dependency error

Bug Description

Let’s assume I have a package my-awesome-package with the following structure:

|-package.json
|+foo
  |+bar
    |-index.js
|-constants.js

So, in my index.js I’d like to use some constants, but for some reason instead of doing

import { PI } from "../../constants";

I prefer to use

import { PI } from "my-awesome-package/constants";

So when I run depcheck it throws a missing dependency error

Versions

• node -v: v8.11.4
• npm -v: 5.6.0
• depcheck -v: 0.6.1

Extra info

I’m not quite sure about how cool using import statements containing own package name is, but it looks ok for me

[phil-lgr]

With Node 16 self reference are supported https://nodejs.org/api/packages.html#self-referencing-a-package-using-its-name, I’m wondering how to handle this with depcheck now

[matz3]

I fully agree with @phil-lgr. This should not cause a missing dependency issue in case the package defines “exports” in the package.json.