Arch Linux User Repository

@j1simon: Pipe it to /dev/null or complain upstream.

It shows too many warnings:

....
==> Iniciando build()...
npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated trim@0.0.1: Use String.prototype.trim() instead
npm WARN deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
npm WARN deprecated rollup-plugin-terser@7.0.2: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated flatten@1.0.3: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated @types/vfile-message@2.0.0: This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed.
npm WARN deprecated @types/localforage@0.0.34: This is a stub types definition for localforage (https://github.com/localForage/localForage). localforage provides its own type definitions, so you don't need @types/localforage installed!
npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated @thornbill/jellyfin-sdk@0.4.1: Use the @jellyfin/sdk package instead.
npm WARN deprecated core-js-pure@3.19.1: core-js-pure@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js-pure.
npm WARN deprecated core-js@3.20.2: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

> jellyfin-web@10.8.9 prepare
> node ./scripts/prepare.js

Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db

Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating
Browserslist: caniuse-lite is outdated. Please run:
  npx browserslist@latest --update-db
....

@z3ntu: PKGBUILD does support an 'all' value for the architecture: it's called any :) It is often used by Python packages.

Jellyfin won't build on armv7h or aarch64 natively due to dependencies. There's no dotnet-sdk-6.0 or aspnet-runtime-6.0 in the repos and I have never gotten them to build properly. You can, however, build jellyfin using dotnet-sdk-6.0-bin and aspnet-runtime-6.0-bin from AUR but you will have to install them first and then modify the PKGBUILD.

EDIT: I'm not even sure you need to modify the PKGBUILD once those packages from AUR are installed. You should just be able to do makepkg -A like @z3ntu said.

@Levitating: You can easily use "makepkg -A" to ignore the "arch" value and just build it. Should make any package work for you. Too bad PKGBUILD doesn't support an "all" value or something like that.

Can you add more architectures (like armv7h)? They should compile fine without any alteration and some weird people are running ArchLinux on their Raspberry Pi's.

Please stop fighting here. I've provided an answer now quite a few comments below. If the AUR helper is broken with this not-so-edge case it's not my problem. Feel free to suggest a solution but until then please stop spamming the comments here.

No I never said I knew everything, you made that assumption here.. Fixing the issue fixes the real issue instead of just avoiding it and being toxic..

Since you know better than everyone else, fork the package and maintain it yourself. That solves everyone's problem here.