Tauri Plugin Connectivity

Cross-platform network connectivity detection for Tauri 2.x apps.

This plugin provides a unified API for querying network connection status, including connection type (WiFi, Ethernet, Cellular), metered/constrained flags, and reachability. It is designed to help apps make network policy decisions.

Features

• Detect connection type (WiFi, Ethernet, Cellular)
• Query metered and constrained status for network policy decisions
• Check internet reachability
• Cross-platform support (Windows, Linux, macOS, iOS, Android)

Platform	Supported
Windows	Yes
Linux	Yes
macOS	Yes
Android	Yes
iOS	Planned

Getting Started

Installation

1. Install NPM dependencies:

   npm install

2. Build the TypeScript bindings:

   npm run build

3. Build the Rust plugin:

   cargo build

Tests

Run all tests (TypeScript and Rust):

npm test

Run TypeScript tests only:

npm run test:ts

Run Rust tests only:

cargo test --workspace --lib

Manual Linux scenario testing

See Linux Connectivity Manual Testing for WSL2, VirtualBox, NetworkManager, ModemManager, metered, constrained, and transport-type test scenarios.

Install

This plugin requires a Rust version of at least 1.94.0

Rust

Add the plugin to your Cargo.toml:

src-tauri/Cargo.toml

[dependencies]
tauri-plugin-connectivity = { git = "https://github.com/silvermine/tauri-plugin-connectivity" }

JavaScript/TypeScript

Install the JavaScript bindings:

npm install @silvermine/tauri-plugin-connectivity

Usage

Prerequisites

Initialize the plugin in your tauri::Builder:

fn main() {
   tauri::Builder::default()
      .plugin(tauri_plugin_connectivity::init())
      .run(tauri::generate_context!())
      .expect("error while running tauri application");
}

API

Query connection status

import { connectionStatus } from '@silvermine/tauri-plugin-connectivity';

async function checkConnection() {
   const status = await connectionStatus();

   console.debug(`Connected: ${status.connected}`);
   console.debug(`Type: ${status.connectionType}`);
   console.debug(`Metered: ${status.metered}`);
   console.debug(`Constrained: ${status.constrained}`);
}

Make network policy decisions

Use the connection status to defer expensive operations on constrained or metered connections:

import { connectionStatus } from '@silvermine/tauri-plugin-connectivity';

async function shouldDownload(): Promise<boolean> {
   const status = await connectionStatus();

   if (!status.connected) {
      console.debug('No internet connection');
      return false;
   }

   if (status.metered || status.constrained) {
      console.debug('Metered or constrained connection — deferring download');
      return false;
   }

   return true;
}

Use from Rust

Access the connectivity API from any Tauri manager type via the extension trait:

use tauri_plugin_connectivity::ConnectivityExt;

fn check_connection<R: tauri::Runtime>(app: &tauri::AppHandle<R>) {
   match app.connectivity().connection_status() {
      Ok(status) => {
         println!("Connected: {}", status.connected);
         println!("Type: {:?}", status.connection_type);
      }
      Err(e) => eprintln!("Could not detect connection status: {e}"),
   }
}

Connection Status

The connectionStatus() function returns a ConnectionStatus object:

Field	Type	Description
connected	boolean	Whether the device has an active network path
metered	boolean	Whether data usage is billed or limited
constrained	boolean	Whether the connection is data-constrained or restricted
connectionType	ConnectionType	The physical transport: wifi, ethernet, cellular, unknown

Platform mapping

Field	Windows	Linux	macOS	iOS	Android
connected	InternetAccess or ConstrainedInternetAccess	NetworkManager FULL/PORTAL/LIMITED or up IPv4/IPv6 default route fallback	nw_path_get_status == satisfied	NWPath.status satisfied	NET_CAPABILITY_INTERNET
metered	NetworkCostType Unknown/Fixed/Variable	NetworkManager primary device Metered	nw_path_is_expensive	NWPath.isExpensive	absence of NOT_METERED
constrained	ConstrainedInternetAccess, data-limit, roaming, or background data restrictions	NetworkManager portal/limited/metered or cellular roaming; fallback defaults to false	nw_path_is_constrained	NWPath.isConstrained	missing VALIDATED, or Data Saver / RESTRICT_BACKGROUND on a metered active network
connectionType	WWAN/WLAN/IANA interface type	NetworkManager device type or sysfs fallback	nw_path_uses_interface_type	NWInterface.InterfaceType	TRANSPORT_* capabilities

Development Standards

This project follows the Silvermine standardization guidelines. Key standards include:

• EditorConfig: Consistent editor settings across the team
• Markdownlint: Markdown linting for documentation
• Commitlint: Conventional commit message format
• Code Style: 3-space indentation, LF line endings

Running Standards Checks

npm run standards

License

MIT

Contributing

Contributions are welcome! Please follow the established coding standards and commit message conventions.