StatLens:Dependencies

The Dependencies row counts the entries in the manifest files of the project. Its value is the total over all manifest files. Expand it to see one row per file, with its path and its count. Click a file to open it.

If no manifest file is found, the row says no manifest file found.

Supported files

Stat Lens looks at every scanned file with one of these names. Upper and lower case in the file name do not matter. Files in excluded folders, for example in node_modules, are not read. See Scanning.

File	What is counted
package.json	The keys in dependencies and devDependencies. Other sections such as peerDependencies or optionalDependencies are not counted.
requirements.txt	Every line that is not empty and does not start with # or -. Lines with options such as -r other.txt or -e . are therefore not counted.
pyproject.toml	See pyproject.toml below.
*.csproj	Every <PackageReference> element.

A project with several manifest files, for example a monorepo with one package.json per package, gets one row per file. The rows are sorted by path.

pyproject.toml

The file is read line by line without a full TOML parser. These entries are counted:

• PEP 621: the strings in dependencies = [...] in the [project] table, and in every group in [project.optional-dependencies]. Arrays on one line and arrays over several lines both work.
• Poetry: every key in [tool.poetry.dependencies], [tool.poetry.dev-dependencies] and [tool.poetry.group.<name>.dependencies]. The python entry is not counted.

When a file is skipped

A manifest file that cannot be read is left out of the list without a warning. This also happens when a package.json is not valid JSON.