tools: remove unneeded tool in update-eslint.sh

Trott · Trott · commit 80b300e80608 · 2021-11-28T13:54:39.000-08:00
The tool to remove absolute paths from package.json files is no longer
necessary. It appears that npm no longer stores these paths, or at least
not in a way that causes the kind of churn we saw in the past.
diff --git a/tools/update-eslint.sh b/tools/update-eslint.sh
@@ -27,9 +27,6 @@ rm -rf node_modules/eslint
     "$NODE" "$NPM" exec -- dmn@2.2.2 -f clean
     # TODO: Get this into dmn.
     find node_modules -name .package-lock.json -exec rm {} \;
-    # Use removeNPMAbsolutePaths to remove unused data in package.json.
-    # This avoids churn as absolute paths can change from one dev to another.
-    "$NODE" "$NPM" exec -- removeNPMAbsolutePaths@1.0.4 .
 )
 
 mv eslint-tmp/node_modules/eslint node_modules/eslint

Original file line number	Diff line number	Diff line change
`@@ -27,9 +27,6 @@ rm -rf node_modules/eslint`
`27`	`27`	`"$NODE" "$NPM" exec -- dmn@2.2.2 -f clean`
`28`	`28`	`# TODO: Get this into dmn.`
`29`	`29`	`find node_modules -name .package-lock.json -exec rm {} \;`
`30`		`- # Use removeNPMAbsolutePaths to remove unused data in package.json.`
`31`		`- # This avoids churn as absolute paths can change from one dev to another.`
`32`		`- "$NODE" "$NPM" exec -- removeNPMAbsolutePaths@1.0.4 .`
`33`	`30`	`)`
`34`	`31`
`35`	`32`	`mv eslint-tmp/node_modules/eslint node_modules/eslint`