closes#5161
The root cause of such issues:
`vue-jscodeshift-adapter` requires `vue-template-compiler`.
`vue-template-compiler` tries to require the `vue` package and check
its version on startup.
Normally, there's no `vue` package in the dependency tree of `@vue/cli`,
so this check will just skip.
But if the user has installed some other global package that depend on
`vue`, and hoists it to the root `node_modules`, `vue-template-compiler`
would successfully require it and check against that `vue` version,
which sometimes may be outdated, thus failing the bootstrap process.
Currently, if we use `api.extendPackage({foo: null}, {prune: true})` the dependency is removed but a warning is logged as the range is invalid:
```
WARN invalid version range for dependency "foo":
- null injected by generator "my-plugin"
```
* chore: switch to leven
* chore: update lock file
* chore: iterate through all the available commands and find closest match
* chore: update yarn.lock
* fix: lint
* chore: find the best possible match
* fix: should infer package manager from config if there's no lockfile in the project
* fixup! fix: should infer package manager from config if there's no lockfile in the project
Currently, 3 options are implemented:
- options.prune (defaults to `false`) - Remove null or undefined
fields from the object after merging.
- options.merge (defaults to `true`) deep-merge nested fields, note
that dependency fields are always deep merged regardless of this option.
- options.warnIncompatibleVersions (defaults to `true`) Output warning
if two dependency version ranges don't intersect.
Closes#4779
* feat: lock minor versions when creating projects / adding plugins
closes#5012
* refactor: also calculate latestMinor version
* feat: support add packages with tilde version range
* refactor: make the `runCommand` invocations more concise
* refactor: use the `getVersions` utility function to get latestMinor
* feat: when adding plugins, use tilde range by default
* fix: allow empty args
