Dependabot's bump fails the build: vite.config.js defined the global apiRoot
as a template literal evaluated on every read (the backend address lives in
localStorage and the address dialog changes it), and Vite 5+ only accepts a
literal in define. The global is a getter on window now, installed by a plugin
imported first in main.js, returning the same expression on every read; the
call sites are untouched.
The card header put the server name, the subscription name and the group tag
on one flex row: a long tag such as "PROXY - 负载均衡 (2)" squeezed the name
into two lines while staying centred against them, and the subscription name
wrapped wherever the row broke. Bulma's small message also pads the header
and the body differently, so a gap opened under the title and the body text
sat a step further in.
The name takes the row, a tag that does not fit drops to its own line, the
subscription name always sits under both, and header and body share their
padding.
The card asked for 65rem. The root font is 0.9em up to 1400px and 16px above
it, so on any wider viewport — a 200% display scaling or a zoomed-out window
gets there — 65rem is 1040px while the wrapper Buefy sizes the dialog with is
capped at 960px: the card ran 80px past it and the close button, which sits on
the wrapper's corner, ended up in the middle of the header. 60rem is 960px at
the 16px root and never wider than the wrapper.
"HOST(2) (info)" becomes "HOST (2) · info". The handle that brings the status
sidebar back was a 36px glyph in a shadowed box, the largest control on a
phone screen; it is a 32px target with a tooltip now.
The list header printed the Subscription-Userinfo header as
"download: 0 GB; upload: 0 GB; total: 107 GB; expire: 2026-10-04 18:59 UTC"
and then, after a "|", the provider's own STATUS= line with the same numbers
in GiB and a Go-formatted timestamp. The header is the standard form: when it
is present it is rendered alone as "Used 1.78 GiB / 100.00 GiB · Expires
2026-10-04" (GiB throughout, the day in local time); the STATUS= text is used
only when the provider sends no header.
#1973 raised golang.org/x/net to v0.54.0, which removed http2.TrailerPrefix;
google.golang.org/grpc v1.57.1 still referenced it, so `go build ./...` in
service/ failed:
grpc@v1.57.1/internal/transport/handler_server.go:242:18: undefined: http2.TrailerPrefix
grpc v1.84.0 (with protobuf v1.36.11 and the matching genproto) builds against
it; go mod tidy moved x/net to v0.57.0 and x/crypto to v0.54.0 along the way.
The navbar and the login dialog showed logo2.png, a raster wordmark that
blurred on 2x displays and needed a colour filter to survive the dark theme.
The brand is now the circular icon as SVG with the name as text, so it
renders sharp at every size and takes the navbar's colour in both themes; on
narrow phones the name goes first, then the icon.
The favicon is the SVG with a multi-size .ico fallback, and the PWA-era PNGs,
the tile icon and the Windows installer icon are rendered from the same file.
Without --log-file the viewer said "log printed to console, please see log in
console", which the Windows service, the launchd job and every "log to
console" setup cannot do. The logger now also keeps its last 4 MiB in memory
and the viewer reads that tail when there is no file; the lines carry the
same timestamp and level prefix as the file adapter's.
The log area also gave way to nothing: at 50vh a short window pushed the
filters and the export button below the fold with only a scrollbar to hint at
them. It now shrinks so the footer stays visible.
The installer writes {app}\v2rayA_env.txt with the log file and the asset
directory and points at it with a machine-wide environment variable, then
starts the service — which runs with the Service Control Manager's
environment from boot time and does not see the variable until the next
reboot. Until then v2rayA logged nowhere and looked for assets in the config
directory, and the web log viewer showed only "log printed to console".
When neither the variable nor --win-envfile is given, look for the file where
the installer puts it: the executable's parent directory, then its own.
lucide-static's stylesheet declares eot, woff2, woff, ttf and a legacy SVG
font for all 2112 icons, so Vite copied every format into web/ and the
embedded binary grew from about 26 MB to 48 MB; the SVG font alone is 20 MB of
glyph outlines. The interface uses 44 icons.
A Vite plugin (gui/build/lucide-subset.mjs) scans src/ for icon names — class
usage, icon props, dialog options and the Buefy pack's internalIcons — subsets
lucide.woff2 to those glyphs with subset-font and serves the result as a
virtual stylesheet with the 8 KB font inlined. A name the font does not have
fails the build naming it, where it used to render an empty box.
lucide-static's font CSS references all five webfont formats (eot, ttf,
svg, woff, woff2), so Vite emitted ~23 MB of icon fonts into the web panel;
the SVG font alone was ~20.6 MB. All of them render the same glyphs.
scripts/lucide-font.mjs now regenerates src/assets/lucide-font.css from the
upstream CSS with a woff-only @font-face (woff is supported by every
browser since IE9) and runs automatically via the prebuild/preserve hooks,
so a lucide-static upgrade stays in sync. The build output drops from
~23 MB of font files to a single ~414 KB woff while keeping all icon
classes.
The vendored core/xray submodule is dropped. xray-core is now pinned via a
go mod pseudo-version resolving to v26.7.28 (commit 5ca6f4b7); v26 tags are
not directly resolvable because Xray's module path lacks the /v26 suffix, so
the pin must be made by commit hash. CI workflows and the AUR PKGBUILD no
longer need "submodules: recursive" / "git submodule update".
The juicity and tuic outbounds are ported from softwind to
github.com/daeuniverse/outbound (temporarily replaced with an olicesx fork
pending sticky-ip support):
- Dialer calls use DialContext; the network string is decoded with
netproxy.ParseMagicNetwork instead of a "udp" prefix check, since it may
be binary-encoded via netproxy.MagicNetwork.
- A packetConnAdapter wraps xray's UDP dial result: outbound asserts the
underlay conn to netproxy.PacketConn whose ReadFrom/WriteTo signatures
(netip.AddrPort / string) differ from net.PacketConn, while xray returns
*internet.PacketConnWrapper.