v0.6.0

Bridge v0.6.0

This release introduces a shared analytics platform for Bridge, providing a consistent, privacy-first analytics experience across both web and desktop applications. Analytics infrastructure has been centralized into a dedicated package, reducing application complexity while establishing a scalable foundation for future analytics enhancements.

📊 Shared Analytics Package

Bridge now includes a new @bridge/analytics package that serves as the single source of truth for analytics across the entire platform.

Highlights

• Added a new shared @bridge/analytics package.
• Unified analytics integration across web and desktop applications.
• Introduced a provider-agnostic analytics architecture.
• Added centralized error tracking support.
• Reduced direct analytics dependencies within applications.
• Added comprehensive analytics documentation and developer tooling.

Provider-Agnostic Architecture

Analytics is now abstracted behind a shared AnalyticsClient interface.

Benefits include:

• Decoupled application code from analytics vendors.
• Easier adoption of alternative analytics providers in the future.
• Consistent APIs for event tracking and user identification.
• Shared analytics behavior across all Bridge applications.

The current implementation uses PostHog internally, with all provider-specific logic isolated to a dedicated provider module.

Singleton Analytics Client

The analytics package uses a singleton architecture:

• Eliminates the need for React context-based analytics management.
• Supports usage from both React and non-React code.
• Provides a single analytics client instance across applications.
• Simplifies analytics initialization and consumption.

---

🔒 Privacy-First Error Tracking

Bridge now includes centralized client-side error tracking with safeguards designed to minimize sensitive data collection.

Global Error Monitoring

Added support for:

• Uncaught JavaScript errors (window.onerror)
• Unhandled promise rejections (unhandledrejection)

Restricted Error Metadata

To maintain a privacy-first approach, captured request metadata intentionally excludes:

• Request URLs
• HTTP headers
• Authentication tokens
• Request bodies
• Other potentially sensitive request data

This ensures analytics focuses on application reliability rather than user content.

---

🌐 Web Application Migration

The web application has been migrated to the shared analytics platform.

Analytics Provider

• Added a new AnalyticsProvider.
• Replaced the existing PostHogProvider.
• Moved analytics initialization into the shared package.
• Simplified analytics usage throughout the application.

Configuration Improvements

Analytics configuration now uses environment variables instead of hardcoded values:

• Added POSTHOG_HOST
• Added POSTHOG_API_KEY

This improves deployment flexibility and environment-specific configuration management.

Dependency Cleanup

• Added @bridge/analytics.
• Removed direct posthog-js dependency.
• Removed @posthog/react.
• Consolidated analytics logic into the shared package.

---

🖥️ Desktop Analytics Support

The desktop application now includes analytics support powered by the shared package.

Desktop Integration

• Added a desktop-specific AnalyticsProvider.
• Wrapped the application with analytics initialization.
• Added application launch tracking.
• Added application close tracking.
• Tagged desktop analytics events with app: "desktop" metadata.

Desktop-Aware Tracking

Analytics behavior is adapted for the Tauri environment:

• Disables pageview capture.
• Disables pageleave capture.
• Preserves analytics features relevant to desktop applications.

Environment-Based Configuration

Desktop analytics can be enabled using:

• VITE_POSTHOG_PROJECT_TOKEN
• VITE_POSTHOG_HOST

When configuration is unavailable:

• Analytics is automatically disabled.
• Applications continue functioning normally.
• A warning is logged to assist developers.

---

⚙️ Analytics Infrastructure

Several foundational analytics capabilities were added to support future product insights.

Typed Events

• Added strongly typed analytics event constants.
• Improved TypeScript safety for event tracking.
• Centralized event definitions within the analytics package.

React Integration

• Added a reusable useAnalytics hook.
• Simplified analytics access throughout React applications.
• Standardized analytics usage patterns across platforms.

PostHog Autocapture

Bridge now relies on PostHog autocapture for:

• Browser detection
• Operating system detection
• Session tracking
• Page views (web only)
• Click interactions

This reduces custom tracking code while improving consistency.

---

✅ Quality & Reliability

• Added comprehensive TypeScript support throughout the analytics package.
• Verified successful type checking for packages/analytics.
• Verified successful type checking for apps/web.
• Verified successful type checking for apps/desktop.
• Reduced analytics-related duplication across applications.
• Established a shared analytics foundation for future platform growth.

---

What's Changed

• feat(analytics): introduce shared @bridge/analytics package
• feat(analytics): add provider-agnostic analytics client and singleton architecture
• feat(analytics): add privacy-first error tracking and typed events
• feat(analytics): add reusable React analytics hooks
• feat(web): migrate from PostHogProvider to shared AnalyticsProvider
• feat(desktop): add desktop analytics integration and lifecycle tracking
• refactor(web): move analytics configuration to environment variables
• refactor(web): remove direct PostHog dependencies
• refactor(analytics): isolate PostHog implementation behind provider abstraction
• docs(analytics): add comprehensive package documentation

Full Changelog: v0.5.0...v0.6.0

v0.5.0

Bridge v0.5.0

This release focuses on improving response handling, large payload performance, and desktop usability. Bridge can now safely render and download extremely large API responses while providing a more resilient experience for local API testing and desktop workflows.

🚀 Large Response Handling & Downloads

Bridge now intelligently handles large and extremely large HTTP responses, preventing browser freezes while maintaining access to response data.

Highlights

• Added safe rendering safeguards for large API responses.
• Introduced paginated chunk viewing for extremely large payloads.
• Added native Save As downloads across desktop and browser environments.
• Improved response viewer performance and memory usage.
• Added user-friendly warnings when responses exceed safe rendering thresholds.

Smart Response Limits

Bridge now automatically categorizes responses based on size:

• Large Responses (> 500 KB)

  • Display a warning notice before rendering.
  • Allow users to choose between viewing or downloading the response.

• Extremely Large Responses (> 5 MB)

  • Use chunked pagination for safer viewing.
  • Disable expensive formatting operations to reduce memory consumption.
  • Prevent HTML preview rendering that could freeze the browser.

Native Save As Downloads

Downloading responses now uses the best available platform experience:

• Tauri Desktop

  • Native Save As dialog support.
  • Direct filesystem writes through Tauri APIs.

• Modern Browsers

  • Uses the File System Access API where available.
  • Allows selecting destination folders and custom filenames.

• Fallback Support

  • Automatic Blob downloads for unsupported browsers.

User-cancelled downloads are now handled gracefully without errors.

Chunked Response Viewer

For extremely large responses, Bridge now provides:

• 1 MB response pagination.
• Faster navigation through large payloads.
• Persistent download actions.
• Improved responsiveness when inspecting large datasets.

---

🖥️ Improved Local API Testing

Testing local services is now more intuitive across desktop and browser environments.

Local API Notices

Bridge now detects local API endpoints and displays helpful guidance when requests target localhost or private network services.

Desktop Integration

• Added Tauri environment detection utilities.
• Added support for opening URLs directly from the desktop application.
• Improved handling of unreachable local endpoints.
• Added clearer notifications for connection failures.

---

🎨 UI & Component Enhancements

Several reusable UI components have been added and refined to improve consistency throughout the application.

New Components

• Added InputGroup for structured input layouts.
• Added Textarea component for flexible multiline input.

Response Viewer Improvements

• Added loading state enhancements.
• Improved response metadata presentation.
• Added status-based color indicators.
• Refined chunked viewer navigation and controls.

Design Updates

• Improved button styling consistency across the application.
• Enhanced spacing, layout, and interaction patterns.
• Better visual feedback for response state and actions.

---

✅ Quality & Reliability

• Improved TypeScript safety throughout response handling logic.
• Added defensive rendering safeguards for large payloads.
• Verified successful TypeScript compilation across packages.
• Verified production builds for web targets.
• Improved stability when working with large API responses and local services.

---

What's Changed

• feat(response): add safe rendering and native downloads for large responses
• feat(response): introduce chunked viewing for extremely large payloads
• feat(desktop): add local API detection and desktop URL integration
• feat(ui): add InputGroup and Textarea components
• refactor(response): improve metadata display and status handling
• style(ui): refine button consistency and response viewer experience

Full Changelog: v0.4.0...v0.5.0

v0.4.0

Bridge v0.4.0

This release introduces two major improvements to the Bridge workspace experience: interoperable exports and built-in documentation for requests, folders, and collections.

✨ Export Collections, Folders, and Requests

Bridge now supports exporting collections, folders, and individual requests directly from the sidebar.

Highlights

• Export collections, folders, and requests from the sidebar via the new More menu.
• Added a confirmation dialog before export to prevent accidental downloads.
• Introduced a flexible export architecture that supports multiple export formats.
• Exports now generate standardized JSON documents for improved portability and interoperability.

OpenAPI Export (Default)

Bridge now exports to OpenAPI 3.0.3 by default, making exported APIs compatible with:

• Swagger
• Postman
• Insomnia
• Bruno
• Other OpenAPI-compatible tooling

Files are exported using clean JSON filenames based on the entity name.

Additional Export Formats

The new exporter framework also includes support for:

• Bridge JSON (round-trip compatible)
• Postman Collection v2.1
• OpenAPI 3.0.3

The exporter system is fully extensible, allowing additional formats to be added without UI changes.

Round-Trip Compatible Bridge Exports

Bridge exports now include hosted JSON schemas and can be imported back into Bridge without losing structure or metadata, enabling reliable backup and sharing workflows.

Sidebar Improvements

To support export actions, sidebar controls have been redesigned:

• Row actions now use Edit and More controls instead of separate icon buttons.
• Collections, folders, and requests now share a cleaner context menu experience.
• Delete actions have been moved into the More menu alongside Export.

---

📝 Rich Text Documentation

Bridge now includes built-in documentation capabilities powered by a reusable rich text editor.

Request Documentation

Requests now include a dedicated Docs tab where you can:

• Write endpoint documentation
• Add implementation notes
• Describe request behavior and usage
• Store rich text content alongside requests

Collection & Folder Overviews

Collections and folders now include an Overview tab for documenting:

• API architecture
• Team conventions
• Authentication requirements
• Project notes and onboarding information

Rich Text Editor Features

The new editor includes:

• Bold, italic, underline, and strikethrough formatting
• Headings and text alignment
• Code formatting
• Lists and blockquotes
• Live formatting state indicators
• Responsive light and dark mode support

Multiple Editing Modes

Switch seamlessly between:

• Edit – WYSIWYG rich text editing
• Preview – Read-only rendered output
• HTML – Direct HTML editing powered by Monaco Editor

Persistence Improvements

Documentation content is now fully integrated across the application:

• Request descriptions are preserved when saving requests and examples.
• Collection and folder descriptions save automatically through configuration updates.
• Imported requests correctly populate documentation content.
• Exported entities retain documentation metadata.

---

✅ Quality & Reliability

• Added hosted JSON schemas for exported Bridge documents.
• Improved importer compatibility for exported Bridge collections and requests.
• Fixed editor synchronization when switching between Preview and Edit modes.
• Verified TypeScript compilation and type safety across all updated packages.

What's Changed

• feat: introduce rich text editor with docs and overview tabs #8
• feat(export): add interoperable export for collections, folders, and requests #7

Full Changelog: v0.3.0...v0.4.0

v0.3.0

Bridge v0.3.0

Bridge 0.3.0 introduces a major upgrade to how requests and collections are imported, navigated, and shared between the web and desktop applications. This release adds first-class support for importing Postman Collections and OpenAPI specifications, route-based navigation across the web app, and deep-linking support for the desktop client.

🚀 Highlights

Universal API Collection Importer

Bridge now supports importing API definitions from multiple formats through a unified import experience:

• Import cURL commands
• Import Postman Collections
• Import OpenAPI / Swagger specifications (JSON or YAML)
• Automatic format detection
• Drag-and-drop file imports
• Collection preview before import
• Syntax-aware editor with automatic language detection

Imported collections are automatically converted into native Bridge workspaces, folders, and requests, making migration from existing API tools significantly easier.

Route-Based Navigation for Web

The web application now supports URL-based navigation and state synchronization.

You can now:

• Open workspaces directly via URL
• Link to specific folders and requests
• Use browser bookmarks for API resources
• Navigate with browser back/forward controls
• Share URLs with teammates

The application state stays synchronized with the URL while maintaining the same workflow and behavior as the desktop application.

Desktop Deep Linking

Bridge desktop now supports deep links using the bridge:// protocol.

Examples:

• bridge://workspace/{workspaceId}/request/{requestId}
• bridge://workspace/{workspaceId}/folder/{folderId}/request/{requestId}

This enables:

• Opening specific requests directly in the desktop app
• Seamless transitions between web and desktop experiences
• Deep-link powered workflows and integrations

A new Open in Desktop action has also been added to the web application, allowing users to instantly open the current workspace or request in the native client.

✨ Improvements

Import Experience

• New drag-and-drop import workflow

• File picker support for JSON and YAML files

• Collection tree preview before import

• Improved OpenAPI parsing, including:

  • Server URL extraction
  • Path parameter conversion
  • Query parameter defaults
  • Operation metadata support

• Unified importer architecture shared across web and desktop clients

Navigation & State Management

• Persistent sidebar expansion state
• Improved workspace and folder navigation
• Request tabs now synchronize with route changes
• Eliminated route transition flickering and unnecessary reloads
• Better handling of browser history and bookmarked URLs

Platform Consistency

• Shared navigation behavior across web and desktop
• Shared importer package used throughout the monorepo
• Improved compatibility between native and browser experiences

🛠️ Technical Notes

• Introduced the new shared package: @bridge/importer
• Added OpenAPI 3.x and Swagger 2.0 parsing support
• Added bidirectional route synchronization for Next.js
• Added Tauri deep-link integration for desktop applications
• Expanded request and folder metadata to support OpenAPI-specific fields

What's Changed

• feat(importer): introduce unified API collection import architecture (#3)
• feat(routing): support direct navigation to workspaces, folders, and requests (#5)
• feat(desktop): support workspace and request navigation via deep links (#6)

Full Changelog: v0.2.0...v0.3.0

v0.2.0

Full Changelog: v0.1.14...v0.2.0

v0.1.14

Full Changelog: v0.1.13...v0.1.14

v0.1.13

Full Changelog: v0.1.12...v0.1.13

v0.1.0

Full Changelog: https://github.com/jaideepghosh/bridge/commits/v0.1.0