How to check if the current process is running Tauri (not web only)?

[boan-anbo]

Is there an equivalent to is-electron or other native means to check if it's current running in Tauri?

[FabianLars]

you can check for the __TAURI__ object: if (window.__TAURI__) {}

[simonhyll]

Depends on how advanced you want to make it. Personally I use an approach that relies on compiling a WASM library differently depending on whether or not I'm compiling for Tauri support. The most reliable solution is some manner of conditional compilation of your code, whether you do it with Webpack, Vite or WASM is entirely up to you. Checking for __TAURI__ however on the window object is probably the easiest solution however, possibly waiting to run any commands that check for it until the page is fully loaded just to be sure.

[joepio]

I think that window.__TAURI__ is only available when build.withGlobalTauri is enabled, since a release or two. So it might be better to use window.__TAURI_METADATA__, which should always be available.

Incorrect, may be a bug.

[FabianLars]

I think that window.TAURI is only available when build.withGlobalTauri is enabled, since a release or two.

Nope, not the case. I think what you're seeing here is that you're navigating/redirecting to external urls? In that case only __TAURI_METADATA__ and __TAURI_POST_MESSAGE__ will be left, which is a bug! Sooner or later (as-in, in some future release) these 2 won't be available after redirect anymore either.

[joepio]

I think what you're seeing here is that you're navigating/redirecting to external urls?

I'm not doing that in my app, so that should not be the case. So I guess what I'm seeing is a bug then! Anyways, for me checking window.__TAURI_METADATA__ works at this moment, and window.__TAURI__ does not.

[akiross]

Is this answer still valid for v2?

Edit: apparently not.

[akiross]

In v2, it seems from this answer that window.__TAURI_INTERNALS__ might be set in tauri.

[unlocomqx]

(v2) also works

import {isTauri} from "@tauri-apps/api/core"