Lucas Fernandes Nogueira f1637d62df refactor(examples): remove unused files (#3762) 3 lat temu
..
.scripts a6def7066e Refactor(tauri): move tauri-api and tauri-updater to tauri (#1455) 4 lat temu
scripts d36c8e0322 Fix importing `@tauri-apps/api` in Node.js (#3752) 3 lat temu
src f1637d62df refactor(examples): remove unused files (#3762) 3 lat temu
test be096623bf feat(updater): refactor in-memory (#37) 3 lat temu
.license_template 22d1803b77 chore(license): purge template path because not everyone is a robot (#1462) 4 lat temu
CHANGELOG.md fbb9017840 Apply Version Updates From Current Changes (#3512) 3 lat temu
Cargo.toml f1637d62df refactor(examples): remove unused files (#3762) 3 lat temu
LICENSE_APACHE-2.0 319cf16a54 fix: prune packages, add license files, closes #1507 (#1769) 4 lat temu
LICENSE_MIT 319cf16a54 fix: prune packages, add license files, closes #1507 (#1769) 4 lat temu
README.md 319cf16a54 fix: prune packages, add license files, closes #1507 (#1769) 4 lat temu
build.rs aba3238146 feat(core): add cfg alias for the updater feature 3 lat temu

README.md

Tauri

status Chat Server devto

devto

support

Component Version
tauri

About Tauri

Tauri is a polyglot and generic system that is very composable and allows engineers to make a wide variety of applications. It is used for building applications for Desktop Computers using a combination of Rust tools and HTML rendered in a Webview. Apps built with Tauri can ship with any number of pieces of an optional JS API / Rust API so that webviews can control the system via message passing. In fact, developers can extend the default API with their own functionality and bridge the Webview and Rust-based backend easily.

Tauri apps can have custom menus and have tray-type interfaces. They can be updated, and are managed by the user's operating system as expected. They are very small, because they use the system's webview. They do not ship a runtime, since the final binary is compiled from rust. This makes the reversing of Tauri apps not a trivial task.

This module

This is the glue crate that holds everything together. It brings the runtimes, macros, utilities and API into one final product. It reads the tauri.conf.json file at compile time in order to bring in features and undertake actual configuration of the app (and even the Cargo.toml file in the project's folder). It handles script injection (for polyfills / prototype revision) at runtime, hosts the API for systems interaction, and even manages updating.

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

Semver

tauri is following Semantic Versioning 2.0.

Licenses

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

MIT or MIT/Apache 2.0 where applicable.

Logo: CC-BY-NC-ND