Configuration¶
rescript.json¶
Add @rescript-tauri/core to the dependencies key. ReScript 12 renamed the legacy bs-dependencies to dependencies; the bs--prefixed key is still accepted but deprecated.
{
"name": "my-app",
"dependencies": ["@rescript-tauri/core"],
"package-specs": [{ "module": "esmodule", "in-source": true }],
"suffix": ".res.mjs"
}
If you enable "namespace": true in your own package, @rescript-tauri/core modules remain accessible under the Tauri namespace top-level re-export (see docs/functional-design.md §2.8).
peerDependencies¶
@rescript-tauri/core declares the following peerDependencies so you can pin the upstream versions:
Peer |
Range |
|---|---|
|
|
|
|
|
|
@rescript/core 1.6.0+ has a peerDependencies.rescript of >=11.1.0, which fully covers ReScript 12.x.
Compatibility matrix¶
Component |
Supported range |
|---|---|
Tauri |
2.x (matches the |
ReScript |
>= 12.0.0 (uncurried-by-default) |
|
>= 1.6.0 |
Node.js |
Active LTS |
OS |
Linux / macOS / Windows (Tauri 2.x desktop targets) |
ReScript 11 is not supported. The decision and rationale are recorded in PRD §10 row 7 and the corresponding steering document.
Top-level Tauri re-export¶
Tauri.res re-exports a curated subset of modules so you can open Tauri and reach the most common entry points without long paths.
open Tauri
let result = await Core.Raw.invoke("greet", ~args={"name": "World"})
The re-export set (confirmed 2026-05-09 — PRD §10 row 1):
In |
Reach via |
|---|---|
|
|
|
|
|
|
|
|
|
|
Not in |
Why |
|---|---|
|
Utility namespace; 31 helpers would shadow user names |
|
Process metadata; explicit |
|
Sized opaque types; explicit |
|
Opaque resource handle; explicit lifecycle |
|
Heavy with sub-modules ( |
|
Test-only |
Add-on packages¶
Add-on packages are each independently versioned and published.
They declare both @rescript-tauri/core and the matching upstream
library as peerDependencies.
Package |
Upstream peer |
Status |
Guide |
|---|---|---|---|
|
|
merged; |
|
|
|
merged; |
|
|
|
merged; |
rescript-struct is not supported (deprecated upstream;
see RFC-0002 §2.1).