Readme correction

[morpheus133]

Fixes

• README Bug: Corrected the file exclusion for building the web app. gulpfile.js was incorrectly excluded instead of gulpfile.babel.js. (Fix Commit)

Improvements

• Added Latest Version: Updated the README to include the latest release version (release-10.10.z). (Improvement Commit)

• Split Build Instructions: Separated build instructions for Jellyfin Web 10.8- and 10.9+ for clarity and ease of use. (Improvement Commit)

[dmitrylyzo]

1. Name the commit 1 as a6a72c8

Update Jellyfin Web branch

or

Update Jellyfin Web branch to 10.10.z

2. Name the commit 2 as

Split build instructions for Jellyfin Web 10.8- and 10.9+

Simplified the process by splitting the instructions for easier copying.
Included steps for 10.8- for completeness, despite its likely lower usage.

Tbf, I'm not sure about the log message (long part) and whether this splitting is even necessary (because this also requires fixing the Windows wiki, which has Command line and PowerShell commands).

3. Name the commit 3 as

Exclude gulpfile from packaging

gulpfile.js was renamed in 6a6a14cb9b3a6016db0a469aa3f14bdfc8a861d0

[morpheus133]

Tbf, I'm not sure about the log message (long part) and whether this splitting is even necessary (because this also requires fixing the [Windows wiki](https://github.com/jellyfin/jellyfin-tizen/wiki/Build-on-Windows#build-jellyfin-web), which has Command line and PowerShell commands).

Updating the wiki is necessary because of the gulpfile.
While we’re at it, I’d add this as well.
Here is the PR for that:
#324

[dmitrylyzo]

Updating the wiki is necessary because of the gulpfile.

Yes, but what I meant was, is the splitting 10.8/10.9 really worth?
SKIP_PREPARE simply has no effect on 10.9+, and USE_SYSTEM_FONTS has no effect on 10.8-, so you can use one set of commands for both.
Also, as you note, 10.8- is unlikely to be used in the future. Moreover, we always drop support of the previous major release (10.9 after 10.10 is out). So maybe we should just remove everything related to 10.8-.

If we are going to continue splitting command sets, I think the remark blocks are a bit blended.
We could wrap them with collapsible blocks:

mockup begin

Build Jellyfin Web

For version 10.9+:

cd jellyfin-web
npm ci --no-audit
USE_SYSTEM_FONTS=1 npm run build:production

USE_SYSTEM_FONTS=1 is required to discard unused fonts and to reduce the size of the app. (Since Jellyfin Web 10.9)

For version 10.8-:

cd jellyfin-web
SKIP_PREPARE=1 npm ci --no-audit
npm run build:production

SKIP_PREPARE=1 is needed for version 10.8-.

You should get jellyfin-web/dist/ directory.

Use npm run build:development if you want to debug the app.

If any changes are made to jellyfin-web/, the jellyfin-web/dist/ directory will need to be rebuilt using the command above.

mockup end

It is still not perfect, but 🤷

[morpheus133]

... Also, as you note, 10.8- is unlikely to be used in the future. Moreover, we always drop support of the previous major release (10.9 after 10.10 is out). So maybe we should just remove everything related to 10.8-.

Than the easiest is to remove it.
10.10 is working with tizen so no reason to keep/use older versions.
If somebody need it than check it in the README history.