KeelrLeek
4179247203
0.1.0-alpha.2 bumped three version strings with a tool that writes UTF-8
WITH a BOM, and committed it. Neither build survives that:
package.json vitefu JSON.parses the raw string, so `npm run dev`
exited instantly — "Unable to read package.json"
tauri.conf.json the Tauri build script failed with "expected value at
line 1 column 1"; cargo exit 101
Cargo.toml tolerated, but wrong
`require()` hides this. Node strips a BOM on require and JSON.parse does
not, so reading package.json from a REPL reports a perfectly good file
while both builds refuse it. Only the raw bytes show it: EF BB BF.
All 191 tracked files scanned. These three were the only ones affected,
and they are exactly the three 5682dfc touched. Stripped with Node rather
than PowerShell, whose default Out-File/Set-Content encoding is what wrote
them in the first place — the files are byte-identical but for the three
leading bytes.
Cargo.lock carries the 0.1.0-alpha.1 -> alpha.2 propagation the release
commit left behind in the working tree.
34 lines
798 B
TOML
34 lines
798 B
TOML
[workspace]
|
|
resolver = "2"
|
|
members = [
|
|
"src-tauri",
|
|
"crates/soulseek-proto",
|
|
"crates/soulseek-client",
|
|
"crates/player",
|
|
"crates/tagger",
|
|
"crates/metadata",
|
|
"crates/library",
|
|
]
|
|
|
|
[workspace.package]
|
|
version = "0.1.0-alpha.2"
|
|
edition = "2021"
|
|
rust-version = "1.77.2"
|
|
authors = ["Trifecta Solutions"]
|
|
|
|
[workspace.dependencies]
|
|
tokio = { version = "1", features = ["rt-multi-thread", "net", "io-util", "sync", "time", "macros", "fs"] }
|
|
bytes = "1"
|
|
thiserror = "2"
|
|
serde = { version = "1.0", features = ["derive"] }
|
|
serde_json = "1.0"
|
|
log = "0.4"
|
|
image = { version = "0.25", default-features = false, features = ["jpeg", "png", "webp"] }
|
|
|
|
[profile.dev]
|
|
# Peer connections + audio decode are unusably slow at opt-level 0.
|
|
opt-level = 1
|
|
|
|
[profile.dev.package."*"]
|
|
opt-level = 2
|