2.0.0

Bugfixes

• Fix linking of localy available packages, when they are also a sub-dependency (see below)

Breaking changes

This breaking change applies only to the following scenario:

• linking is not disabled
• at some point somewhere you have a dependency on package xyz
• xyz has a (sub-)dependency on a package, that is actually localy avaliable (regardless of the version)

before:

That sub-dependency gets installed from the registry to the main node_modules

my-modular-app
├── modules
│   ├── database (@2.0.0)
│   └── tasks (@2.0.0) [requires xyz, which in return requires database@^1.0.0]
├── node_modules
│   ├── minstall
│   ├── database (@1.0.0 from registry)
│   └── tasks -> ../modules/tasks
├── index.js
└── package.json [requires minstall, database@2.0.0 and tasks@2.0.0]

now (if linking is enabled):

The localy avaliable package will be linked in the main node_modules

my-modular-app
├── modules
│   ├── database (@2.0.0)
│   └── tasks (@2.0.0) [requires xyz, which in return requires database@1.0.0]
├── node_modules
│   ├── minstall
│   ├── database ../modules/database
│   └── tasks -> ../modules/tasks
├── index.js
└── package.json [requires minstall, database@2.0.0 and tasks@2.0.0]

notice how before, database@1.0.0 was installed, but the local package not linked, and now
the local package is linked, but database@1.0.0 not installed.

The reasoning is, that when linking packages, you usually do that for development purposes,
but without that change, some localy avaliable packages might not get linked