fix(installer): Fix patch conflict with newer pnpm versions (#44)

This commit is contained in:
megumin 2022-10-04 21:36:46 +01:00 committed by GitHub
parent dafbd39113
commit e010b2d63e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 6 additions and 6 deletions

View file

@ -36,7 +36,7 @@ Don't close your terminal just yet!
Now to patch vencord into your Discord client, run the following command and follow the interactive prompt.
```sh
pnpm patch
pnpm run patch
```
Now fully close Discord. Start and confirm Vencord successfully installed by checking if you have a new Vencord section in Settings.
@ -45,7 +45,7 @@ If you ever need to get back to the Vencord folder, just open a new terminal and
All plugins are disabled by default, so your first step should be opening Settings and enabling the plugins you want.
You can unpatch Vencord using `pnpm unpatch`
You can unpatch Vencord using `pnpm run unpatch`
## Installing on Browser

View file

@ -56,7 +56,7 @@ async function install(installations) {
console.log("Failed to give write perms to Discord Flatpak.");
console.log(
"Try running this script as an administrator:",
"sudo pnpm patch"
"sudo pnpm run patch"
);
process.exit(1);
}
@ -71,7 +71,7 @@ async function install(installations) {
console.error("No write access to", selected.location);
console.error(
"Try running this script as an administrator:",
"sudo pnpm patch"
"sudo pnpm run patch"
);
process.exit(1);
}

View file

@ -42,7 +42,7 @@ async function uninstall(installations) {
console.error("No write access to", selected.location);
console.error(
"Try running this script as an administrator:",
"sudo pnpm unpatch"
"sudo pnpm run unpatch"
);
process.exit(1);
}