Search Criteria
Package Details: webcord 4.9.1-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/webcord.git (read-only, click to copy) |
---|---|
Package Base: | webcord |
Description: | A Discord and SpaceBar Electron-based client implemented without Discord API |
Upstream URL: | https://github.com/SpacingBat3/WebCord |
Keywords: | discord electron spacebar webcord |
Licenses: | MIT |
Submitter: | Hanabishi |
Maintainer: | Hanabishi |
Last Packager: | Hanabishi |
Votes: | 37 |
Popularity: | 1.61 |
First Submitted: | 2021-11-06 15:32 (UTC) |
Last Updated: | 2024-05-03 21:01 (UTC) |
Dependencies (3)
- electron30 (electron30-binAUR)
- esbuild (esbuild-gitAUR) (make)
- npm (corepackerAUR) (make)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »
ThePenguinUser commented on 2022-07-06 08:30 (UTC)
After trying to update to the latest 3.4.0 release I get a signing error. ==> Making package: webcord 3.4.0-1 (Wed 06 Jul 2022 10:25:47 AM CEST) ==> Retrieving sources... -> Downloading WebCord-3.4.0.tar.gz... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 169k 0 169k 0 0 113k 0 --:--:-- 0:00:01 --:--:-- 212k -> Found run.sh -> Found buildInfo.json -> Found app.desktop ==> Validating source files with sha256sums... WebCord-3.4.0.tar.gz ... FAILED run.sh ... Passed buildInfo.json ... Passed app.desktop ... Passed ==> ERROR: One or more files did not pass the validity check! -> error downloading sources: webcord context: exit status 1
==> Making package: webcord 3.4.0-1 (Wed 06 Jul 2022 10:25:50 AM CEST) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found WebCord-3.4.0.tar.gz -> Found run.sh -> Found buildInfo.json -> Found app.desktop ==> Validating source files with sha256sums... WebCord-3.4.0.tar.gz ... FAILED run.sh ... Passed buildInfo.json ... Passed app.desktop ... Passed ==> ERROR: One or more files did not pass the validity check! -> error making: webcord
Hanabishi commented on 2022-05-29 18:29 (UTC)
Ok.
SpacingBat3 commented on 2022-05-29 18:22 (UTC) (edited on 2022-06-02 14:37 (UTC) by SpacingBat3)
Probably it is not the best idea for now to use
electron>={X}
andelectron<{Y}
overelectron{X}
, as this won't work well with Electron packages provided incommunity
repository. And I saw that AUR packages still provides bothelectron{X}
andelectron={X}
. And the current Electron dependency format does not give any advantage overelectron{X}
, unless you would like to provide a range of Electron major releases, giving users a possibility to choose the Electron version to install.medzik commented on 2022-05-27 18:51 (UTC)
sources/code/common/modules/l10n.ts(3,19): error TS7016: Could not find a declaration file for module '@spacingbat3/jsonc-parser'. '/mnt/build/makepkg/webcord/src/WebCord-3.1.4/node_modules/@spacingbat3/jsonc-parser/dist/jsoncParser.js' implicitly has an 'any' type. Try
npm i --save-dev @types/spacingbat3__jsonc-parserif it exists or add a new declaration (.d.ts) file containing
declare module '@spacingbat3/jsonc-parser';``Hanabishi commented on 2022-03-12 18:15 (UTC)
Ok, you caught me right before pushing the update.
SpacingBat3 commented on 2022-03-12 18:09 (UTC) (edited on 2022-05-22 18:15 (UTC) by SpacingBat3)
@Hanabishi consider using
electron{X}
for Electron versioning in general, since it seems to be present in case of both Arch Linux official and AUR Electron packages.electron
in reality either means the latest Electron version available or any Electron package available since there're packages in AUR that provideselectron
while might be unsupported by WebCord (althrough it should work on Electron version from range 13-17 and I can give a support for any still maintained major release from that range).SpacingBat3 commented on 2021-12-12 17:11 (UTC) (edited on 2021-12-12 17:13 (UTC) by SpacingBat3)
I've updated the repository and
disable-updates-check.patch
won't be needed in the next minior update (2.2.X
) – instead, you can use the build flags to disable the notifications but does not disable the update check (so the one could still check the console for the updates). You can already test that by cloning the repository, changing its version to any lower than the latest stable ones and packaging the app with Electron Forge andWEBCORD_UPDATE_NOTIFICATIONS
enviroment variable set tofalse
. See documentation for further information how you can implement this in your code.« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »