Can't Build Jellyfin-web.

[kstoev]

This issue respects the following points:

• This issue is not already reported on GitHub (I've searched it).
• I agree to follow Jellyfin's Code of Conduct.
• This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.

Describe the bug

npm install isn't working.

Reproduction Steps

1. git clone https://github.com/jellyfin/jellyfin-web.git
2. cd jellyfin-web
3. npm install

Expected/Actual behaviour

No issues.

Logs

PS E:\jellyfin-web> npm install
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 @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 source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm warn deprecated flatten@1.0.3: flatten is deprecated in favor of utility frameworks such as lodash.
npm warn deprecated @stylelint/postcss-markdown@0.36.2: Use the original unforked package instead: postcss-markdown
npm warn deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecatednpm warn deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm warn deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm warn deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm warn deprecated @stylelint/postcss-css-in-js@0.37.3: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

added 1840 packages, and audited 1841 packages in 26s

34 vulnerabilities (1 low, 23 moderate, 10 high)

To address issues that do not require attention, run:
npm audit fix

To address all issues possible (including breaking changes), run:
npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run npm audit for details.

Server version

latest

Web version

latest

Build version

latest

Platform

WINDOWS 10

Browser

Firefox

Additional information

No response

[thornbill]

Warnings are not errors. Those can be ignored. Also running install only installs dependencies but does not build the app. You can find build instructions in the README.

[anultravioletaurora]

Can confirm that the npm install output is just a series of warnings. I was able to start the web project successfully