Arch Linux User Repository

nodejs v24.10.0 or higher is required to build vrcx, it might be worth adding >=24.10.0 to nodejs in makedepends

patching the package.json to rename it to lowercase causes part of vrcx to write it's files to a separate directory (both VRCX and vrcx exist in ~/.config/). is this expected behavior? is this intentional?

A quick investigation revealed that uppercase files are those that should be backed up (such as the main sqlite3 database or JSON files), while lowercase files appear to be temporary files created for Electron's operation.

I confirmed that when moved via --config, uppercase files are not created. While these should be avoided from being placed in the config directory as they're temporary files, there's no actual harm occurring at present, so we'll leave them as is. Thank you for the report.

oh also with a new version being out you might wanna update pkgver to 2026.01.04. i updated the version and commented out that patching, so ill report any issues if they occur.

Thank you. If this keeps happening in the future, reporting it in a comment when marking it as out-of-date will be sufficient.

oh also with a new version being out you might wanna update pkgver to 2026.01.04. i updated the version and commented out that patching, so ill report any issues if they occur.

patching the package.json to rename it to lowercase causes part of vrcx to write it's files to a separate directory (both VRCX and vrcx exist in ~/.config/). is this expected behavior? is this intentional?

vrcx aur package update into v2025.12.06.

Through our testing with multiple contributors, we've confirmed that upgrading to dotnet10 is safe when accompanied by a build. Currently, since dotnet-runtime-10 is still only in the AUR, we're using dotnet-runtime (which is available in extra). We will update when either dotnet-runtime-10 becomes available in extra or when dotnet 11 is released—we'll make this change at an appropriate time (since VRCX will likely be updated before then, we anticipate few issues).

@xuan25 thanks! Actually, the patch application method has changed again, so we'll confirm with maintainers before updating. It should be ready within a few days. https://codeberg.org/kazu0617/vrcx-aur/pulls/3

The patch for suppressing auto-updates might need to be updated. E.g.

--- a/src/stores/vrcxUpdater.js
+++ b/src/stores/vrcxUpdater.js
@@ -48,7 +48,7 @@ export const useVRCXUpdaterStore = defineStore('VRCXUpdater', () => {
         }

         const [autoUpdateVRCX, vrcxId] = await Promise.all([
-            configRepository.getString('VRCX_autoUpdateVRCX', 'Auto Download'),
+            configRepository.getString('VRCX_autoUpdateVRCX', 'Off'),
             configRepository.getString('VRCX_id', '')
         ]);

You may find the discussion in PR #1414 helpful: https://github.com/vrcx-team/VRCX/pull/1414

Oh, I messed up.
This is code for testing automatic update disabling, and I usually use echo “$pkgver” > Version.
Due to the design of CI/CD, when VRCX is obtained from the source code, the Version file always points to the previous version, so it needs to be corrected.

why the echo "2021.01.01" > Version? Now VRCX doesn't know that it's in the latest version, and it's asking me to update