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, [email protected] and [email protected]]

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 [email protected]]
├── node_modules
│   ├── minstall
│   ├── database ../modules/database
│   └── tasks -> ../modules/tasks
├── index.js
└── package.json [requires minstall, [email protected] and [email protected]]

notice how before, [email protected] was installed, but the local package not linked, and now
the local package is linked, but [email protected] 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

1.6.1

Improvements

• Better install-as-dependency detection
• Better compatibility for modules as dependencies, that have local packages with the same names as local packages from the parent
• Improved cleanup after install-as-dependency
• Better support for scoped-packages on install-as-dependency

1.6.0

New Features

• added --no-link and --loglevel flags

1.5.0

Changelog

New Features

• Support for local modules as dependencies in other local modules.
  aka. if your local module A requires your local module B, B wont be downloaded, but linked, if the local version of B matches A's dependency
• Minstall now allows . as module-folder
  for when you just want to install and link a bunch of modules, that don't have a parent-project (this is experimental, please open an issue if this feature leads to problems)

Bugfixes

• Fix handling of scoped local modules
• local scoped modules are now linked using their scoped-names, no matter what the folder they are actually in is called

Improvements

• Updated the version of fs-extra minstall uses to 2.0.0
• some code cleanup

1.4.0

Changelog

Bugfixes

• Fix installing a package as dependency with minstall-postinstall (see #16)

1.3.7

Changelog

Bugfixes

• Fix already linked modules from a previous installation not being deleted before reinstall

Improvements

• Add stdout-log to output when a command from within minstall fails

1.3.6

Changelog

Bugfixes

• Fix installing of conflicting scoped dependencies

1.3.3

Changelog

Bugfixes

• Fix wrong module-folder usage

1.3.2

Changelog

Improvements

• Greatly improve logs. npm-warnings are now silenced (errors are still shown though)

1.3.1

Changelog

New Features

• minstall now installs conflicting dependencies correctly, but gives a hint that the user might try to use non-conflicting package-versions
• minstall now better detects, when it's started from the wrong folder, and exits without doing anything

Bugfixes

• through the use of fs-extra instead of fs, the filesystem-operations are now easier and less prone to error

Improvements

• Code cleanup