Skip to content

Commit 05f2dee

Browse files
New translations publishing.md (Chinese Traditional)
1 parent a344ae4 commit 05f2dee

File tree

1 file changed

+60
-0
lines changed

1 file changed

+60
-0
lines changed
Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
id: publishing
3+
title: "App publishing"
4+
sidebar_label: App publishing
5+
---
6+
7+
8+
## Build your UI Assets
9+
Now that you are ready to package your project, you will need to instruct your framework to create the assets.
10+
11+
SVELTE using yarn:
12+
```
13+
yarn rollup -c
14+
```
15+
16+
REACT-CREATE-APP using npm
17+
```
18+
npm run craco build
19+
```
20+
21+
QUASAR using global `@quasar/cli`
22+
```
23+
quasar build
24+
```
25+
26+
## tauri bundler
27+
Make certain that you have installed that tauri bundler:
28+
```
29+
cargo tauri-cli -v
30+
```
31+
If you do not see a version number being reported, then you must install the bundler:
32+
33+
```
34+
$ cargo install tauri-cli --force
35+
```
36+
37+
> Note: We chose to call this bundler `tauri-cli` because in the near future we will be providing a **rust-only** entry point to tauri.
38+
39+
## Inform tauri about your distributables location
40+
Be sure that you have configured the `src-tauri/tauri.conf.json` to correctly point at the assets. Edit `src-tauri/tauri.conf.json`:
41+
42+
```
43+
{
44+
"build": {
45+
"distDir": "../build"
46+
}
47+
}
48+
```
49+
50+
## Run `tauri build`
51+
```
52+
local: yarn tauri build
53+
global: tauri build
54+
```
55+
56+
Like the dev window, the first time you run this, it will take some time to collect the rust crates and build everything - but on subsequent runs it will only need to rebuild the tauri crates themselves.
57+
58+
Because of the way that rust builds its targets, the final app is placed in the following folder:
59+
60+
`src-tauri/target/release/bundle`

0 commit comments

Comments
 (0)