aboutsummaryrefslogtreecommitdiff
path: root/packages/bun-cli/reset-bin.js
diff options
context:
space:
mode:
authorGravatar Jarred Sumner <jarred@jarredsumner.com> 2021-10-28 05:34:38 -0700
committerGravatar Jarred Sumner <jarred@jarredsumner.com> 2021-10-28 05:34:38 -0700
commita44cb9708f8a1460a2851bc3357d2cec655f7ee2 (patch)
tree3e1e31d0cd13f86228d493635e41dfe66e1c84e6 /packages/bun-cli/reset-bin.js
parentc7fc08056ac2588c2305017e1c6d0677bdb69448 (diff)
downloadbun-a44cb9708f8a1460a2851bc3357d2cec655f7ee2.tar.gz
bun-a44cb9708f8a1460a2851bc3357d2cec655f7ee2.tar.zst
bun-a44cb9708f8a1460a2851bc3357d2cec655f7ee2.zip
New subcommand: `bun upgrade`. It upgrades bun to the latest version.
Diffstat (limited to 'packages/bun-cli/reset-bin.js')
-rwxr-xr-xpackages/bun-cli/reset-bin.js13
1 files changed, 0 insertions, 13 deletions
diff --git a/packages/bun-cli/reset-bin.js b/packages/bun-cli/reset-bin.js
deleted file mode 100755
index 233061ef2..000000000
--- a/packages/bun-cli/reset-bin.js
+++ /dev/null
@@ -1,13 +0,0 @@
-#!/usr/bin/env node
-throw new Error(`bun-cli: Failed to install correctly
-
-Make sure you don't have "ignore-scripts" set to true. You can check this with
-"npm config get ignore-scripts". If that returns true you can reset it back to
-false using "npm config set ignore-scripts false" and then reinstall bun.
-
-If you're using npm v7, make sure your package-lock.json file contains either
-"lockfileVersion": 1 or the code "hasInstallScript": true. If it doesn't have
-either of those, then it is likely the case that a known bug in npm v7 has
-corrupted your package-lock.json file. Regenerating your package-lock.json file
-should fix this issue.
-`);