TREK 3.1 overhauls backend, adds passkey login, maps upgrade, and better expense splitting

TREK 3.1 introduces several major changes for users planning a travel with real-time collaboration, interactive maps, packing lists, and much more. The most substantial change is a complete backend migration from Express to NestJS, accompanied by a frontend upgrade to React 19; both segments now share a single Zod contract package, ensuring alignment between requests and responses.

Alongside these architectural revisions, 18 vulnerabilities have been resolved, including a critical authentication bypass. Cost tracking has been redesigned into a Splitwise-style shared expense tracker crafted for group trips, providing an easier way to manage expenses. Security and accessibility are further improved: users may now register passkeys and log in with Face ID, Touch ID, or security keys.

Building on core trip planning, two-way flight synchronization with AirTrail is now available. Day routes displayed on maps use real road networks with travel-time connectors, replacing straight-line estimates. Users can discover and add points of interest from OpenStreetMap and Overpass directly on the planner map, while support for an instance-wide Mapbox token is included. The transport planner now supports additional types, such as bus, taxi, bicycle, and ferry.

Following these upgrades, booking confirmations can be imported using KDE Itinerary, and improvements are seen in the dashboard, packing lists, translation coverage, and the redesigned, offline-ready progressive web app. Minor enhancements and bug fixes are also present in this update.