* Revert "fix: disable reusing existing package-lock.json when upgrading (#1530)"

This reverts commit 2728e399.

* switch from —package-lock-only to —ignore-scripts

Removing `--package-lock-only` option from npm installs due to https://github.com/npm/npm/issues/19852

Pretty sure this fixes #1495

This has been causing undesirable side-effects with sub-dependencies “rolling back” in long-running PRs.

Fixes #1532

Skip writing package-lock.json locally before `npm install —package-lock-only` to work around https://github.com/npm/npm/issues/19852

Workaround to fix #1528

Fixes #1320

This reverts commit a28cef0a.

Check if a lock file already exists in the current *branch* and if so then use it as the base for generating the new lock file and not the master one. Ensures that simple rebases result in same result.

Closes #1481

* Revert "fix: Revert "feat: lerna bootstrap support (#1486)""

This reverts commit 4e592d60.

* fix: fix lerna.json detection

This reverts commit 3cab59d2.

Adds support for running `lerna bootstrap` instead of `npm install` or `yarn install` (without Workspaces), hence allowing support of internally-linked dependencies.

Closes #1441, Closes #1443

This reverts commit f0111101.

Adds a config option to bot administrators called `exposeEnv`, for cases where repositories are trusted. If set to true, the bot's full `process.env` can be used for `.npmrc` variable substitution and is passed to child processes when generating lock files. Disabled by default, including in the App.

This reverts commit 1aba7c79.

Fixes #1425

This feature adds support for pnpm shrinkwrap.yaml files.

Closes #1391

* chore(deps): update dependency prettier to v1.9.0

* run prettier

If we have in a package.json links to some local lib file:../path/to/folder
Then the local lib package.json will be copied to the tmp folder to be able to generate the right yarn lock file. This is not working with tgz files, only folder reference.

Closes #1215 

Use `upath` for windows-friendly path joins.

Closes #1203

* refactor: don’t store yarn.lock content in packageFile

* chore: don’t log full lockfile

* refactor: don’t save package-lock.json

* update tests

Remove original getFile, getFileContent, and getFileJson and replace with getFile (which used to be getFileContent.. shortened now for convenience). Also remove unused getSubdirectories functions.

Previously, upgrades with failing lock files were not raised as PRs. Usually this is because of missing private module configuration. Now, Renovate will raise a PR but add a comment warning of the error, with the error log. It's raised as a comment because we now won't need to regenerate the lock file error every run, and we don't want to "lose" it if the PR description gets updated.

Closes #600 

* refactor: await fs.readFile instead of sync version

* fix: replace fs and tmpDir sync with promises

It appears that writing the existing lockfile before regenerating a new one can help speed some resolutions up.

Closes #815

* fix: write npmrc to subdirectories with lock file

* fix lint

Previously, Renovate assumed that any yarn workspaces configuration would be in the root of the repository. Now, workspaces can be located within a subdirectory, e.g. `frontend/`. Note: Renovate still supports only one workspace per repository, please file an issue if you require more than one.

Closes #842