From 6faf09be4a717bfcd5d4a74166e59faa374b1376 Mon Sep 17 00:00:00 2001
From: Jon Surrell <sirreal@users.noreply.github.com>
Date: Fri, 12 Jan 2024 12:27:19 +0100
Subject: [PATCH] Remove check-latest-npm validation

---
 bin/check-latest-npm.js | 134 ----------------------------------------
 bin/tsconfig.json       |   1 -
 package.json            |   3 +-
 3 files changed, 1 insertion(+), 137 deletions(-)
 delete mode 100644 bin/check-latest-npm.js

diff --git a/bin/check-latest-npm.js b/bin/check-latest-npm.js
deleted file mode 100644
index 8b9f86e95dd567..00000000000000
--- a/bin/check-latest-npm.js
+++ /dev/null
@@ -1,134 +0,0 @@
-#!/usr/bin/env node
-
-/**
- * External dependencies
- */
-const { green, red, yellow } = require( 'chalk' );
-const { get } = require( 'https' );
-const { spawn } = require( 'child_process' );
-const semver = require( 'semver' );
-
-/**
- * Internal dependencies
- */
-const {
-	engines: { npm: npmRange },
-	// Ignore reason: `package.json` exists outside `bin` `rootDir`.
-	// @ts-ignore
-} = require( '../package.json' );
-
-/**
- * Returns a promise resolving with the version number of the latest available
- * version of npm.
- *
- * @return {Promise<string>} Promise resolving with latest npm version.
- */
-async function getLatestNPMVersion() {
-	return new Promise( ( resolve, reject ) => {
-		get(
-			'https://registry.npmjs.org/npm',
-			{
-				headers: {
-					// By passing a specialized `Accept` header, the registry
-					// will return an abbreviated form of the package data which
-					// includes enough detail to determine the latest version.
-					//
-					// See: https://github.com/npm/registry/blob/HEAD/docs/responses/package-metadata.md
-					Accept: 'application/vnd.npm.install-v1+json',
-				},
-			},
-			async ( response ) => {
-				if ( response.statusCode !== 200 ) {
-					return reject(
-						new Error( 'Package data for npm not found' )
-					);
-				}
-
-				let body = '';
-				for await ( const chunk of response ) {
-					body += chunk.toString();
-				}
-
-				let data;
-				try {
-					data = JSON.parse( body );
-				} catch {
-					return reject(
-						new Error(
-							'Package data for npm returned invalid response body'
-						)
-					);
-				}
-
-				const versions = Object.values( data[ 'dist-tags' ] );
-
-				resolve( semver.maxSatisfying( versions, npmRange ) );
-			}
-		).on( 'error', ( error ) => {
-			if (
-				/** @type {NodeJS.ErrnoException} */ ( error ).code ===
-				'ENOTFOUND'
-			) {
-				error =
-					new Error( `Could not contact the npm registry to determine latest version.
-
-This could be due to an intermittent outage of the service, or because you are not connected to the internet.
-
-Because it is important that \`package-lock.json\` files only be committed while running the latest version of npm, this commit has been blocked.
-
-If you are certain of your changes and desire to commit anyways, you should either connect to the internet or bypass commit verification using ${ yellow(
-						'git commit --no-verify'
-					) } .` );
-			}
-
-			reject( error );
-		} );
-	} );
-}
-
-/**
- * Returns a promise resolving with the version number of the local installed
- * version of npm.
- *
- * @return {Promise<string>} Promise resolving with local installed npm version.
- */
-async function getLocalNPMVersion() {
-	return new Promise( async ( resolve ) => {
-		// 'npm' doesn't work correctly on Windows.
-		// https://github.com/WordPress/gutenberg/issues/22484
-		const command = process.platform === 'win32' ? 'npm.cmd' : 'npm';
-		const childProcess = spawn( command, [ '-v' ] );
-
-		let output = '';
-		for await ( const chunk of childProcess.stdout ) {
-			output += chunk.toString();
-		}
-
-		resolve( output.trim() );
-	} );
-}
-
-Promise.all( [ getLatestNPMVersion(), getLocalNPMVersion() ] )
-	.then( ( [ latest, local ] ) => {
-		if ( latest !== local ) {
-			throw new Error(
-				`The local npm version does not match the expected latest version. Expected ${ green(
-					latest
-				) }, found ${ red( local ) }.
-
-It is required that you have the expected latest version of npm installed in order to commit a change to the package-lock.json file.
-
-Run ${ yellow(
-					`npm install --global npm@${ latest }`
-				) } to install the expected latest version of npm. Before retrying your commit, run ${ yellow(
-					'npm install'
-				) } once more to ensure the package-lock.json contents are correct. If there are any changes to the file, they should be included in your commit.`
-			);
-		}
-	} )
-	.catch( ( error ) => {
-		console.error(
-			'Latest npm check failed!\n\n' + error.toString() + '\n'
-		);
-		process.exitCode = 1;
-	} );
diff --git a/bin/tsconfig.json b/bin/tsconfig.json
index f3d576c178d0c0..48fd553e4c049b 100644
--- a/bin/tsconfig.json
+++ b/bin/tsconfig.json
@@ -17,7 +17,6 @@
 	},
 	"files": [
 		"./api-docs/update-api-docs.js",
-		"./check-latest-npm.js",
 		"./plugin/config.js",
 		"./plugin/commands/changelog.js",
 		"./plugin/commands/performance.js",
diff --git a/package.json b/package.json
index 684f35d408d3c2..aae8275e714ab5 100644
--- a/package.json
+++ b/package.json
@@ -359,8 +359,7 @@
 			"wp-scripts lint-style"
 		],
 		"package-lock.json": [
-			"npm run lint:lockfile",
-			"node ./bin/check-latest-npm.js"
+			"npm run lint:lockfile"
 		],
 		"packages/*/package.json": [
 			"wp-scripts lint-pkg-json"