Package Details: bs-manager-git v1.5.2.r95.gcaf7989-1

Git Clone URL: https://aur.archlinux.org/bs-manager-git.git (read-only, click to copy)
Package Base: bs-manager-git
Description: An all-in-one tool for managing Beat Saber versions, maps, mods, and more
Upstream URL: https://github.com/Zagrios/bs-manager
Licenses: GPL
Conflicts: bs-manager
Provides: bs-manager
Submitter: Insprill
Maintainer: Insprill
Last Packager: Insprill
Votes: 2
Popularity: 0.035337
First Submitted: 2023-08-09 04:15 (UTC)
Last Updated: 2025-03-15 00:36 (UTC)

Dependencies (3)

Required by (0)

Sources (2)

Latest Comments

1 2 Next › Last »

Insprill commented on 2025-03-11 03:56 (UTC)

The ERR_MODULE_NOT_FOUND error when installing has been fixed 🥳

hotleanbeef commented on 2025-03-08 18:51 (UTC)

I had the same error as @Jademonas and adding nvm use 22 to the build step in PKGBUILD got it working.

yobson commented on 2025-02-10 15:39 (UTC) (edited on 2025-02-10 15:39 (UTC) by yobson)

it also still fails for me with paru but works if i clone and makepkg -si so i think it's a paru bug. if i add

export NVM_DIR="${srcdir}/.
source /usr/share/nvm/init-nvm.sh || [[ $? != 1 ]]
nvm use 22

to the build step it works with paru when i paru -Bi

sapphire149 commented on 2025-02-10 01:10 (UTC)

@Insprill Still having the same error, even after removing the package from paru cache

Insprill commented on 2025-02-08 20:16 (UTC)

I switched back to nvm. Someone with the error, please ensure you have the latest PKGBUILD, try installing it, and let me know if it works.

yobson commented on 2025-02-08 02:15 (UTC)

just had this error now too when I had not before, it is indeed an issue with the nodejs version being used. you could add nvm as a make dependency and use it to use a specific version of node that is known to be compatible as lots of other AUR packages do. v22.9.0 is what I swapped to and that worked. you can check some of the other packages on the AUR that have nvm as a make dependency to see how they make use of it if you'd like.

MysticBlueWolf commented on 2025-02-01 10:28 (UTC) (edited on 2025-02-02 10:43 (UTC) by MysticBlueWolf)

I had the same error as @Jademonas even with older versions of bs-manager, it seems to be a problem with the latest nodejs package (23.7.0) as downgrading to 23.4.0 solved it for me

Insprill commented on 2025-01-30 18:40 (UTC)

@Jademonas I've had some reports of that error, but I haven't been able to reproduce it myself, and I have no idea what the cause could be. If anyone has any ideas, please share.

Jademonas commented on 2025-01-30 13:36 (UTC) (edited on 2025-01-30 13:41 (UTC) by Jademonas)

Dont know if this is the right place, but i cant install it.

This is the error it gives me:

[webpack-cli] Failed to load '/home/jade/.cache/yay/bs-manager-git/src/bs-manager/.erb/configs/webpack.config.renderer.dev.dll.ts' config [webpack-cli] Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/home/jade/.cache/yay/bs-manager-git/src/bs-manager/.erb/configs/webpack.config.base' imported from /home/jade/.cache/yay/bs-manager-git/src/bs-manager/.erb/configs/webpack.config.renderer.dev.dll.ts at finalizeResolution (node:internal/modules/esm/resolve:275:11) at moduleResolve (node:internal/modules/esm/resolve:860:10) at defaultResolve (node:internal/modules/esm/resolve:984:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:716:12) at #cachedDefaultResolve (node:internal/modules/esm/loader:640:25) at #resolveAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:675:38) at ModuleLoader.resolveSync (node:internal/modules/esm/loader:698:52) at #cachedResolveSync (node:internal/modules/esm/loader:659:25) at ModuleLoader.getModuleJobForRequire (node:internal/modules/esm/loader:387:50) at new ModuleJobSync (node:internal/modules/esm/module_job:342:34) { code: 'ERR_MODULE_NOT_FOUND', url: 'file:///home/jade/.cache/yay/bs-manager-git/src/bs-manager/.erb/configs/webpack.config.base' } npm error code 2 npm error path /home/jade/.cache/yay/bs-manager-git/src/bs-manager npm error command failed

Insprill commented on 2025-01-24 22:26 (UTC)

@yobson That's already fixed, but I forgot to bump the pkgrel. Delete your cached PKGBUILD then update.

1 2 Next › Last »