fix: stay on chalk-cjs instead of picocolors for now

Author: JounQin

.changeset/slow-llamas-fetch.md

@@ -4,5 +4,5 @@
 
 feat: reduce installation size by replacing several dependencies:
 
-- `chalk` -> `picocolors`
+- `chalk` -> `chalk-cjs`
 - `json-stable-stringify` -> `@nolyfill/json-stable-stringify`

package.json

@@ -81,14 +81,14 @@
   "dependencies": {
     "@nolyfill/json-stable-stringify": "^1.0.30",
     "@yarnpkg/lockfile": "^1.1.0",
+    "chalk-cjs": "^5.2.0",
     "ci-info": "^3.7.0",
     "cross-spawn": "^7.0.3",
     "find-yarn-workspace-root": "^2.0.0",
     "fs-extra": "^10.0.0",
     "klaw-sync": "^6.0.0",
     "minimist": "^1.2.6",
     "open": "^7.4.2",
-    "picocolors": "^1.1.1",
     "semver": "^7.5.3",
     "slash": "^3.0.0",
     "tmp": "^0.0.33",

src/applyPatches.ts

@@ -1,6 +1,6 @@
+import colors from "chalk-cjs"
 import { existsSync, writeFileSync } from "fs-extra"
 import { posix } from "path"
-import { blue, bold, cyan, green, red, yellow } from "picocolors"
 import semver from "semver"
 import { hashFile } from "./hash"
 import { logPatchSequenceError } from "./makePatch"
@@ -44,7 +44,7 @@ function getInstalledPackageVersion({
     }
 
     let err =
-      `${red("Error:")} Patch file found for package ${posix.basename(
+      `${colors.red("Error:")} Patch file found for package ${posix.basename(
         pathSpecifier,
       )}` + ` which is not present at ${relative(".", packageDir)}`
 
@@ -53,7 +53,7 @@ function getInstalledPackageVersion({
 
   If this package is a dev dependency, rename the patch file to
   
-    ${bold(patchFilename.replace(".patch", ".dev.patch"))}
+    ${colors.bold(patchFilename.replace(".patch", ".dev.patch"))}
 `
     }
     throw new PatchApplicationError(err)
@@ -64,7 +64,7 @@ function getInstalledPackageVersion({
   const result = semver.valid(version)
   if (result === null) {
     throw new PatchApplicationError(
-      `${red(
+      `${colors.red(
         "Error:",
       )} Version string '${version}' cannot be parsed from ${join(
         packageDir,
@@ -84,9 +84,9 @@ function logPatchApplication(patchDetails: PatchedPackageDetails) {
         })`
       : ""
   console.log(
-    `${bold(patchDetails.pathSpecifier)}@${
+    `${colors.bold(patchDetails.pathSpecifier)}@${
       patchDetails.version
-    }${sequenceString} ${green("✔")}`,
+    }${sequenceString} ${colors.green("✔")}`,
   )
 }
 
@@ -109,7 +109,7 @@ export function applyPatchesForApp({
   const groupedPatches = getGroupedPatches(patchesDirectory)
 
   if (groupedPatches.numPatchFiles === 0) {
-    console.log(blue("No patch files found"))
+    console.log(colors.blue("No patch files found"))
     return
   }
 
@@ -139,10 +139,10 @@ export function applyPatchesForApp({
 
   const problemsSummary = []
   if (warnings.length) {
-    problemsSummary.push(yellow(`${warnings.length} warning(s)`))
+    problemsSummary.push(colors.yellow(`${warnings.length} warning(s)`))
   }
   if (errors.length) {
-    problemsSummary.push(red(`${errors.length} error(s)`))
+    problemsSummary.push(colors.red(`${errors.length} error(s)`))
   }
 
   if (problemsSummary.length) {
@@ -200,8 +200,8 @@ export function applyPatchesForPackage({
         appliedPatches.push(unappliedPatches.shift()!)
       } else {
         console.log(
-          red("Error:"),
-          `The patches for ${bold(pathSpecifier)} have changed.`,
+          colors.red("Error:"),
+          `The patches for ${colors.bold(pathSpecifier)} have changed.`,
           `You should reinstall your node_modules folder to make sure the package is up to date`,
         )
         process.exit(1)
@@ -248,7 +248,9 @@ export function applyPatchesForPackage({
       if (!installedPackageVersion) {
         // it's ok we're in production mode and this is a dev only package
         console.log(
-          `Skipping dev-only ${bold(pathSpecifier)}@${version} ${blue("✔")}`,
+          `Skipping dev-only ${colors.bold(
+            pathSpecifier,
+          )}@${version} ${colors.blue("✔")}`,
         )
         continue
       }
@@ -424,7 +426,10 @@ export function applyPatch({
     const errors: string[] | undefined = bestEffort ? [] : undefined
     executeEffects(forward, { dryRun: false, cwd, bestEffort, errors })
     if (errors?.length) {
-      console.log("Saving errors to", cyan(bold("./patch-package-errors.log")))
+      console.log(
+        "Saving errors to",
+        colors.cyan(colors.bold("./patch-package-errors.log")),
+      )
       writeFileSync("patch-package-errors.log", errors.join("\n\n"))
       process.exit(0)
     }
@@ -458,18 +463,20 @@ function createVersionMismatchWarning({
   path: string
 }) {
   return `
-${yellow("Warning:")} patch-package detected a patch file version mismatch
+${colors.yellow(
+  "Warning:",
+)} patch-package detected a patch file version mismatch
 
   Don't worry! This is probably fine. The patch was still applied
   successfully. Here's the deets:
 
   Patch file created for
 
-    ${packageName}@${bold(originalVersion)}
+    ${packageName}@${colors.bold(originalVersion)}
 
   applied to
 
-    ${packageName}@${bold(actualVersion)}
+    ${packageName}@${colors.bold(actualVersion)}
   
   At path
   
@@ -479,7 +486,7 @@ ${yellow("Warning:")} patch-package detected a patch file version mismatch
   breakage even though the patch was applied successfully. Make sure the package
   still behaves like you expect (you wrote tests, right?) and then run
 
-    ${bold(`patch-package ${pathSpecifier}`)}
+    ${colors.bold(`patch-package ${pathSpecifier}`)}
 
   to update the version in the patch file name and make this warning go away.
 `
@@ -497,8 +504,8 @@ function createBrokenPatchFileError({
   pathSpecifier: string
 }) {
   return `
-${red(bold("**ERROR**"))} ${red(
-    `Failed to apply patch for package ${bold(packageName)} at path`,
+${colors.red(colors.bold("**ERROR**"))} ${colors.red(
+    `Failed to apply patch for package ${colors.bold(packageName)} at path`,
   )}
   
     ${path}
@@ -537,13 +544,15 @@ function createPatchApplicationFailureError({
   pathSpecifier: string
 }) {
   return `
-${red(bold("**ERROR**"))} ${red(
-    `Failed to apply patch for package ${bold(packageName)} at path`,
+${colors.red(colors.bold("**ERROR**"))} ${colors.red(
+    `Failed to apply patch for package ${colors.bold(packageName)} at path`,
   )}
   
     ${path}
 
-  This error was caused because ${bold(packageName)} has changed since you
+  This error was caused because ${colors.bold(
+    packageName,
+  )} has changed since you
   made the patch file for it. This introduced conflicts with your patch,
   just like a merge conflict in Git when separate incompatible changes are
   made to the same piece of code.
@@ -562,8 +571,8 @@ ${red(bold("**ERROR**"))} ${red(
 
   Info:
     Patch file: patches/${patchFilename}
-    Patch was made for version: ${green(bold(originalVersion))}
-    Installed version: ${red(bold(actualVersion))}
+    Patch was made for version: ${colors.green(colors.bold(originalVersion))}
+    Installed version: ${colors.red(colors.bold(actualVersion))}
 `
 }
 
@@ -575,7 +584,9 @@ function createUnexpectedError({
   error: Error
 }) {
   return `
-${red(bold("**ERROR**"))} ${red(`Failed to apply patch file ${bold(filename)}`)}
+${colors.red(colors.bold("**ERROR**"))} ${colors.red(
+    `Failed to apply patch file ${colors.bold(filename)}`,
+  )}
   
 ${error.stack}
 

src/createIssue.ts

@@ -1,5 +1,5 @@
+import colors from "chalk-cjs"
 import open from "open"
-import { bold } from "picocolors"
 import { stringify } from "querystring"
 import { PackageManager } from "./detectPackageManager"
 import { PackageDetails } from "./PackageDetails"
@@ -105,7 +105,7 @@ export function maybePrintIssueCreationPrompt(
   packageManager: PackageManager,
 ) {
   if (vcs) {
-    console.log(`💡 ${bold(packageDetails.name)} is on ${
+    console.log(`💡 ${colors.bold(packageDetails.name)} is on ${
       vcs.provider
     }! To draft an issue based on your patch run
 

src/detectPackageManager.ts

@@ -1,22 +1,22 @@
+import colors from "chalk-cjs"
 import findWorkspaceRoot from "find-yarn-workspace-root"
 import fs from "fs-extra"
-import { bold, red } from "picocolors"
 import process from "process"
 import { join } from "./path"
 
 export type PackageManager = "yarn" | "npm" | "npm-shrinkwrap"
 
 function printNoYarnLockfileError() {
   console.log(`
-${red(bold("**ERROR**"))} ${red(
+${colors.red(colors.bold("**ERROR**"))} ${colors.red(
     `The --use-yarn option was specified but there is no yarn.lock file`,
   )}
 `)
 }
 
 function printNoLockfilesError() {
   console.log(`
-${red(bold("**ERROR**"))} ${red(
+${colors.red(colors.bold("**ERROR**"))} ${colors.red(
     `No package-lock.json, npm-shrinkwrap.json, or yarn.lock file.
 
 You must use either npm@>=5, yarn, or npm-shrinkwrap to manage this project's
@@ -27,8 +27,10 @@ dependencies.`,
 
 function printSelectingDefaultMessage() {
   console.info(
-    `${bold("patch-package")}: you have both yarn.lock and package-lock.json
-Defaulting to using ${bold("npm")}
+    `${colors.bold(
+      "patch-package",
+    )}: you have both yarn.lock and package-lock.json
+Defaulting to using ${colors.bold("npm")}
 You can override this setting by passing --use-yarn or deleting
 package-lock.json if you don't need it
 `,