aboutsummaryrefslogtreecommitdiff
path: root/packages/bun-cli/reset-bin.js
diff options
context:
space:
mode:
authorGravatar Jarred Sumner <jarred@jarredsumner.com> 2021-09-14 16:59:21 -0700
committerGravatar Jarred Sumner <jarred@jarredsumner.com> 2021-09-14 16:59:21 -0700
commit5dbbad5cc42edf6627d0979bc7e40c4ecd72bf20 (patch)
tree89e4dc64f1aa9124bf7190f5b85263f1c2811c20 /packages/bun-cli/reset-bin.js
parent24522f7d743140a8f8be11eac4c2c3458a3fb937 (diff)
downloadbun-5dbbad5cc42edf6627d0979bc7e40c4ecd72bf20.tar.gz
bun-5dbbad5cc42edf6627d0979bc7e40c4ecd72bf20.tar.zst
bun-5dbbad5cc42edf6627d0979bc7e40c4ecd72bf20.zip
Support installing bun from npm
Diffstat (limited to 'packages/bun-cli/reset-bin.js')
-rwxr-xr-xpackages/bun-cli/reset-bin.js13
1 files changed, 13 insertions, 0 deletions
diff --git a/packages/bun-cli/reset-bin.js b/packages/bun-cli/reset-bin.js
new file mode 100755
index 000000000..233061ef2
--- /dev/null
+++ b/packages/bun-cli/reset-bin.js
@@ -0,0 +1,13 @@
+#!/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.
+`);