Lucas Nogueira 6cd6d3fb32 chore(utils): add change file for #7964 1 anno fa
..
.scripts 46e6187c89 chore: update license year (#6311) 2 anni fa
mobile 5848b4e8e9 Fixed channel deserialisation in iOS (#8386) 1 anno fa
scripts 428ea6524c feat(api): expose `Resource` class (#8370) 1 anno fa
src effe5871af fix(core): scope checks on Android (#8420) 1 anno fa
test d5074af562 fix: custom protocol on Windows, change scheme on Android, closes #7801 (#7808) 1 anno fa
CHANGELOG.md 6cd6d3fb32 chore(utils): add change file for #7964 1 anno fa
Cargo.toml 6cd6d3fb32 chore(utils): add change file for #7964 1 anno fa
LICENSE_APACHE-2.0 319cf16a54 fix: prune packages, add license files, closes #1507 (#1769) 4 anni fa
LICENSE_MIT 319cf16a54 fix: prune packages, add license files, closes #1507 (#1769) 4 anni fa
README.md 96d346222f docs: Update Github workflow status shields (#6910) 2 anni fa
build.rs f78e5e4d4a refactor: replace `once_cell` with `std::sync::OnceLock` (#8309) 1 anno fa

README.md

Tauri

status License test core FOSSA Status Chat Server website 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