Repository navigation
Lithium.js v1.6.0 - le tinywiny update fr fr
New:
• Custom search engines - search_engines.register("bing", (query) => "..."), unregistered names fall back to Google instead of breaking navigation
• Header overrides - headers.set for outgoing header overrides, headers.searchEngineHeaders for overrides scoped to just the current search engine's origin
• Device spoofing - headers.device overrides navigator/screen properties (userAgent, platform, screen size, etc.) so the proxied page's own JS sees a different device
• network_log() entries now include a caveats field naming exactly which configured headers got blocked by the browser and why
Changed:
• Repo moved to Lithium-Foundry/Lithium.js, everything updated to match (install commands, error messages, links)
• Added a GitHub Actions workflow that publishes to npm automatically when you cut a GitHub Release
• Referer set via headers.set.referer now gets auto-routed to fetch's real referrer option instead of silently doing nothing
Heads up, not a Lithium limitation:
• Cookie, Host, Origin, anything Sec-/Proxy-, and a few others can't be set from page JS at all, that's a browser restriction (Fetch spec forbidden headers), not something any library can route around
• User-Agent isn't spec-forbidden anymore but Chrome silently drops it from fetch() regardless (old Chromium quirk), Firefox honors it fine
Tested with 270+ checks across server/client/fixtures, all green, no regressions from the last patch. Full details in the README.