From bfb8bccbe83753e527b43c8a3889696087dbe8f1 Mon Sep 17 00:00:00 2001 From: Nathan Fritz Date: Tue, 10 May 2022 12:21:03 -0700 Subject: feat: add flag --omit-lockfile-registry-resolved (#4874) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * feat(arborist): added flag to omit lockfile resolved * feat: add flag --omit-lockfile-registry-resolved Co-authored-by: Caleb ツ Everett --- lib/utils/config/definitions.js | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'lib/utils') diff --git a/lib/utils/config/definitions.js b/lib/utils/config/definitions.js index a5eac8c82..c4be3a658 100644 --- a/lib/utils/config/definitions.js +++ b/lib/utils/config/definitions.js @@ -1385,6 +1385,18 @@ define('omit', { }, }) +define('omit-lockfile-registry-resolved', { + default: false, + type: Boolean, + description: ` + This option causes npm to create lock files without a \`resolved\` key for + registry dependencies. Subsequent installs will need to resolve tarball + endpoints with the configured registry, likely resulting in a longer install + time. + `, + flatten, +}) + define('only', { default: null, type: [null, 'prod', 'production'], -- cgit v1.2.3