Componentpedia / Listings / tauri-runtime-wry

Current Releases

Core

Component	Description	Version	Lin	Win	Mac
tauri	runtime core		✅	✅	✅
tauri-build	applies macros at build-time		✅	✅	✅
tauri-codegen	handles assets, parses tauri.conf.json		✅	✅	✅
tauri-macros	creates macros using tauri-codegen		✅	✅	✅
tauri-runtime	layer between Tauri and webview libraries		✅	✅	✅
tauri-runtime-wry	enables system-level interaction via WRY		✅	✅	✅
tauri-utils	common code used across the tauri crates		✅	✅	✅

Tooling

Component	Description	Version	Lin	Win	Mac
bundler	manufacture the final binaries		✅	✅	✅
tauri-cli	create, develop and build apps		✅	✅	✅
@tauri-apps/cli	Node.js CLI wrapper for tauri-cli		✅	✅	✅
@tauri-apps/api	JS API for interaction with Rust backend		✅	✅	✅

Utilities and Plugins

Component	Description	Version	Lin	Win	Mac
create-tauri-app	Get started with your first Tauri app		✅	✅	✅
vue-cli-plugin-tauri	Vue CLI plugin for Tauri		✅	✅	✅

Introduction

Tauri is a framework for building tiny, blazingly fast binaries for all major desktop platforms. Developers can integrate any front-end framework that compiles to HTML, JS and CSS for building their user interface. The backend of the application is a rust-sourced binary with an API that the front-end can interact with.

The user interface in Tauri apps currently leverages tao as a window handling library on macOS and Windows, and gtk on Linux via the Tauri-team incubated and maintained WRY, which creates a unified interface to the system webview (and other goodies like Menu and Taskbar), leveraging WebKit on macOS, WebView2 on Windows and WebKitGTK on Linux.

To learn more about the details of how all of these pieces fit together, please consult this ARCHITECTURE.md document.

Get Started

If you are interested in making a tauri app, please visit the documentation website. This README is directed towards those who are interested in contributing to the core library. But if you just want a quick overview about where tauri is at in its development, here's a quick burndown:

Platforms

Tauri currently supports development and distribution on the following platforms:

Linux Support

For developing Tauri apps refer to the Getting Started guide on tauri.app.

For running Tauri apps we support the below configurations (these are automatically added as dependencies for .deb and are bundled for AppImage so that your users don't need to manually install them):

• Debian (Ubuntu 18.04 and above or equivalent) with the following packages installed:
  • libwebkit2gtk-4.1-0, libgtk-3-0, libayatana-appindicator3-1¹
• Arch with the following packages installed:
  • webkit2gtk, gtk3, libayatana-appindicator¹
• Fedora (latest 2 versions) with the following packages installed:
  • webkit2gtk3, gtk3, libappindicator-gtk3¹
• Void with the following packages installed:
  • webkit2gtk, gtk+3, libappindicator¹

¹ appindicator is only required if system trays are used

Features

• [x] Desktop Bundler (.app, .dmg, .deb, AppImage, .msi)
• [x] Self Updater
• [x] App Signing
• [x] Native Notifications (toast)
• [x] App Tray
• [x] Core Plugin System
• [x] Scoped Filesystem
• [x] Sidecar

Security Features

• [x] localhost-free (🔥)
• [x] custom protocol for secure mode
• [x] Dynamic ahead of Time Compilation (dAoT) with functional tree-shaking
• [x] functional Address Space Layout Randomization
• [x] OTP salting of function names and messages at runtime
• [x] CSP Injection

Utilities

• [x] Rust-based CLI
• [x] GH Action for creating binaries for all platforms
• [x] VS Code Extension

Development

Tauri is a system composed of a number of moving pieces:

Infrastructure

• Git for code management
• GitHub for project management
• GitHub actions for CI and CD
• Discord for discussions
• Netlify-hosted documentation website
• DigitalOcean Meilisearch instance

Operating systems

Tauri core can be developed on Mac, Linux and Windows, but you are encouraged to use the latest possible operating systems and build tools for your OS.

Contributing

Before you start working on something, it's best to check if there is an existing issue first. It's also a good idea to stop by the Discord server and confirm with the team if it makes sense or if someone else is already working on it.

Please make sure to read the Contributing Guide before making a pull request.

Thank you to everyone contributing to Tauri!

Documentation

Documentation in a polyglot system is a tricky proposition. To this end, we prefer to use inline documentation of Rust code and at JSDoc in typescript / javascript code. We autocollect these and publish them using Docusaurus v2 and netlify. Here is the hosting repository for the documentation site: https://github.com/tauri-apps/tauri-docs

Testing & Linting

Test all the things! We have a number of test suites, but are always looking to improve our coverage:

• Rust (cargo test) => sourced via inline #[cfg(test)] declarations
• Typescript (jest) => via spec files
• Smoke Tests (run on merges to latest)
• eslint, clippy

CI/CD

We recommend you read this article to understand better how we run our pipelines: https://www.jacobbolda.com/setting-up-ci-and-cd-for-tauri/

Organization

Tauri aims to be a sustainable collective based on principles that guide sustainable free and open software communities. To this end it has become a Programme within the Commons Conservancy, and you can contribute financially via Open Collective.

Semver

tauri is following Semantic Versioning 2.0.

Licenses

Code: (c) 2015 - 2021 - The Tauri Programme within The Commons Conservancy.

MIT or MIT/Apache 2.0 where applicable.

Logo: CC-BY-NC-ND

• Original Tauri Logo Designs by Alve Larsson, Daniel Thompson-Yvetot and Guillaume Chau