I’m trying to set up my own copy of Web-Warden, the web interface for Vaultwarden. I downloaded the code from the official repo and followed the instructions in the README. But when I run make full or any other make commands, it fails.
Here’s what I’m seeing:
npm error Lifecycle script `build:oss` failed with error:
npm error code 1
npm error path /home/user/Projects/web-vault/apps/web
npm error workspace @passwordmanager/[email protected]
npm error location /home/user/Projects/web-vault/apps/web
npm error command failed
npm error command sh -c cross-env NODE_OPTIONS="--max-old-space-size=8192" webpack
The error goes on, mentioning issues with build:oss:selfhost:prod and dist:oss:selfhost. It ends with:
FAILED: line 25, exit code 1.
make: *** [Makefile:52: build] Error 1
I haven’t changed any files in the repo. What could be causing this? How can I fix it and get Web-Warden running?
I ran into this exact problem when setting up Web-Warden last month. What finally worked for me was updating my Node.js to the latest LTS version. The older version I had was causing conflicts with some of the dependencies.
After updating Node, I also had to clear my npm cache with ‘npm cache clean --force’ and delete the node_modules folder. Then I ran ‘npm install’ again from scratch.
One other thing to check is your system’s available memory. The error mentions ‘max-old-space-size’, which could indicate your system is running out of memory during the build process. If you’re on a low-spec machine, try closing other memory-intensive applications before running the build.
If none of that works, you might want to check if there are any OS-specific issues. I’ve seen some people have trouble on certain Linux distros due to missing system libraries. The project’s issue tracker on GitHub might have some relevant discussions if that’s the case.
maybe try bumping NODE_OPTIONS max memory to 10240, check ur node/npm versions. if it still fails, clear npm cache or re-clone ur repo. hope this helps!
I encountered a similar issue when setting up Web-Warden. Here’s what worked for me:
First, ensure you’re using a compatible Node.js version. Web-Warden might require a specific version range. Check the package.json file for any version requirements.
If that doesn’t resolve it, try running ‘npm ci’ instead of ‘npm install’ to ensure you’re using the exact dependency versions specified in the package-lock.json file.
Also, consider running the build process with verbose logging enabled. Use ‘npm run build --verbose’ to get more detailed error information. This can help pinpoint the exact step where the build is failing.
If all else fails, you might need to manually install some global dependencies. Sometimes, certain packages need to be installed globally for the build process to work correctly.