Package-lock.json - requires vs dependencies

After reading the answers above, maybe I can put it more simply:

requires can be shared among all other top levels dependencies, while dependencies are standalone, belonging only to the module requiring them.

i.e.

"@angular-devkit/core": "0.8.5","tree-kill": "1.2.0", and "webpack-sources": "1.3.0" do not belong only to the module. They are in the same level as the module requiring them. By contrast, "rxjs": "6.2.2" exists exclusively due to the module requiring it, and it is used only by that module.

By default, npm installs all packages directly in node_modules.

However, let's say that package X is dependent on package Z in version 1.0 and package Y is dependent on the same package Z, but in version 2.0. In this case we have to install two versions of this package. One will be installed in root node_modules folder, and another one will be installed in node_modules folder of dependant package, e.g.

package.json
node_modules
    /X
    /Y
        /node_modules
            /[email protected]
    /[email protected]

Equally likely, npm could build a different, but still correct, package tree:

package.json
node_modules
    /X
        /node_modules
            /[email protected]
    /Y
    /[email protected]

The package-lock.json file will attempt to describe not only the dependencies of your project, but this tree structure as well. Which of the two trees above to build will be encoded in the JSON.

With this knowledge, it's easy to understand:

"requires" reflects dependencies from package.json file of this dependency, while dependencies reflects actually installed dependencies in node_modules folder of this dependency.