mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
unable to build web-vault #1025
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rapkin61 on GitHub (May 3, 2021).
git clone --recurse-submodules https://github.com/bitwarden/web.git web-vault
Cloning into 'web-vault'...
remote: Enumerating objects: 26356, done.
remote: Counting objects: 100% (940/940), done.
remote: Compressing objects: 100% (437/437), done.
remote: Total 26356 (delta 597), reused 775 (delta 485), pack-reused 25416
Receiving objects: 100% (26356/26356), 132.85 MiB | 5.99 MiB/s, done.
Resolving deltas: 100% (19172/19172), done.
Submodule 'jslib' (https://github.com/bitwarden/jslib.git) registered for path 'jslib'
Cloning into '/home/klaus/web-vault/jslib'...
remote: Enumerating objects: 10753, done.
remote: Counting objects: 100% (1253/1253), done.
remote: Compressing objects: 100% (641/641), done.
remote: Total 10753 (delta 724), reused 1029 (delta 574), pack-reused 9500
Receiving objects: 100% (10753/10753), 3.42 MiB | 5.69 MiB/s, done.
Resolving deltas: 100% (7805/7805), done.
Submodule path 'jslib': checked out '4eb50d757d03343ee842ea68a6b2c8282ef3f382'
cd web-vault/
git checkout "$(git tag --sort=v:refname | tail -n1)"
M jslib
Note: checking out 'v2.19.0'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b
HEAD is now at 9d42a565 update jslib
....so ... this is v2.19 - we need to apply patch for that
git apply v2.19.0.patch
npm install
node-sass@4.13.1 install /home/klaus/web-vault/node_modules/node-sass
node scripts/install.js
Downloading binary from https://github.com/sass/node-sass/releases/download/v4.13.1/linux-x64-67_binding.node
Download complete .] - :
Binary saved to /home/klaus/web-vault/node_modules/node-sass/vendor/linux-x64-67/binding.node
Caching binary to /home/klaus/.npm/node-sass/4.13.1/linux-x64-67_binding.node
ngx-infinite-scroll@7.0.1 postinstall /home/klaus/web-vault/node_modules/ngx-infinite-scroll
opencollective postinstall
node-sass@4.13.1 postinstall /home/klaus/web-vault/node_modules/node-sass
node scripts/build.js
Binary found at /home/klaus/web-vault/node_modules/node-sass/vendor/linux-x64-67/binding.node
Testing binary
Binary is fine
webpack-cli@3.2.1 postinstall /home/klaus/web-vault/node_modules/webpack-cli
lightercollective
Please consider donating to our open collective
to help us maintain this package.
https://opencollective.com/webpack/donate
bitwarden-web@2.19.0 postinstall /home/klaus/web-vault
npm run sub:init
bitwarden-web@2.19.0 sub:init /home/klaus/web-vault
git submodule update --init --recursive
error: Your local changes to the following files would be overwritten by checkout:
src/angular/components/register.component.ts
Please commit your changes or stash them before you switch branches.
Aborting
Unable to checkout 'f80e89465ffc004705d2941301c0ffb6bfd71d1a' in submodule path 'jslib'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! bitwarden-web@2.19.0 sub:init:
git submodule update --init --recursivenpm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bitwarden-web@2.19.0 sub:init script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/klaus/.npm/_logs/2021-05-03T09_24_53_641Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! bitwarden-web@2.19.0 postinstall:
npm run sub:initnpm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bitwarden-web@2.19.0 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/klaus/.npm/_logs/2021-05-03T09_24_53_671Z-debug.log
@rapkin61 commented on GitHub (May 3, 2021):
...excuse me for that strange kind of formatting!
How can I switch that off?
@Arathen commented on GitHub (May 5, 2021):
This is a +1 for me as well. Im also getting the exact same error when trying to build the web vault.