Package Details: webcord 4.10.2-1

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: 41
Popularity: 0.53
First Submitted: 2021-11-06 15:32 (UTC)
Last Updated: 2024-10-07 16:36 (UTC)

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 Next › Last »

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 provides electron 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 and WEBCORD_UPDATE_NOTIFICATIONS enviroment variable set to false. See documentation for further information how you can implement this in your code.

Hanabishi commented on 2021-12-09 20:03 (UTC)

Ok, now it works. Updated the package.

SpacingBat3 commented on 2021-12-09 18:15 (UTC)

Oh, the file name should be buildInfo.json, I made a mistake in the documentation... I'll try update it today (in my time zone, which is +0100).

Hanabishi commented on 2021-12-09 05:20 (UTC) (edited on 2021-12-09 05:21 (UTC) by Hanabishi)

@SpacingBat3, I placed buildConfig.json with content

{
    "type": "release"
}

near the package.json, but the app still reports devel mode in About window.

SpacingBat3 commented on 2021-12-08 23:05 (UTC) (edited on 2021-12-08 23:07 (UTC) by SpacingBat3)

@Hanabishi I've finally documented the build flags feature, you can actually implement it if you wish to make PKGBUILD package app as a stable release instead of development release. Please take a look at file below for the further details:

https://github.com/SpacingBat3/WebCord/blob/master/docs/Flags.md#2-other-tools

Hanabishi commented on 2021-12-01 22:17 (UTC) (edited on 2021-12-01 22:20 (UTC) by Hanabishi)

But hey, look how I solved it in the new version.

Hanabishi commented on 2021-12-01 21:46 (UTC)

Electron 15 is still preferred for now

Ok, than I'll keep it for now.

I believe you could just use npm prune --production command

I know, I considered just removing the packages. But there is downside, user will be forced to reinstall packages with every rebuild, which is kinda painful. So I thought to make some trick with installing dev dependencies to separate directory.
But I can do it prune way, if you insist.

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 Next › Last »