InstallOptions configure the generator's behaviour for existing mappings
in the import map. An existing mapping is considered "in-range" if either:
its parent package.json has no "dependencies" range for it
its semver version is within the parent's range
The "latest-compatible version" of a package is the latest existing version
within the parent's "dependencies range", or just the latest existing
version if there is no such range.
"default":
New installs always resolve to the latest compatible version. Existing
mappings are kept unless they are out-of-range, in which case they are
bumped to the latest compatible version.
"latest-primaries":
Existing primary dependencies (i.e. mappings under "imports") are bumped
to latest. Existing secondary dependencies are kept unless they are
out-of-range, in which case they are bumped to the latest compatible
version. New installs behave according to "default".
"latest-all":
All existing mappings are bumped to the latest compatible version. New
installs behave according to "default".
"freeze":
No existing mappings are changed, and existing mappings are always used
for new installs wherever possible. Completely new installs behave
according to "default".
InstallOptions configure the generator's behaviour for existing mappings in the import map. An existing mapping is considered "in-range" if either:
The "latest-compatible version" of a package is the latest existing version within the parent's "dependencies range", or just the latest existing version if there is no such range.
"default": New installs always resolve to the latest compatible version. Existing mappings are kept unless they are out-of-range, in which case they are bumped to the latest compatible version.
"latest-primaries": Existing primary dependencies (i.e. mappings under "imports") are bumped to latest. Existing secondary dependencies are kept unless they are out-of-range, in which case they are bumped to the latest compatible version. New installs behave according to "default".
"latest-all": All existing mappings are bumped to the latest compatible version. New installs behave according to "default".
"freeze": No existing mappings are changed, and existing mappings are always used for new installs wherever possible. Completely new installs behave according to "default".