vite-static 1.2.0

Embed Vite chunks into your Rust application and query them individually.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36

use vite_static::Manifest;

// #[no_embedding] - is an option, that allows you to generate trait implementation, that parses and
// loads chunks on runtime (no chunk and manifest embedding).
//
// This can speed up builds, but it's recommended to embed in release builds.
//
// Note, that:
//  - Manifest is lazy loaded and affter first read never re-read (except if you restart your app).
//  - It does not implement `StaticManifest` (duh), so there's no method to query all chunks at the
//  same time. (Only `Manifest` trait, that should be enough for 99.8% situations).
//  - Chunks are re-read, hash re-computed and mime type is guessed on every function call (chunk,
//  chunk_by_key).

#[derive(Manifest)]
#[vite_dist = "examples/vite-project/dist"]
#[cfg_attr(debug_assertions, no_embedding)] // RECOMMENDED!
// ^- this will add `#[no_embedding]` only on debug builds!
// It's very hard (for some reason) to detect inside proc-macro is this release or debug build.
// So, my solution: you can choose when you want to embed! Win for everybody.
//
// Or you can enable no embedding for every build: (this is library for embedding static, why do you want that?)
// #[no_embedding]
struct MyViteStatic;

fn main() {
    let entry1 = MyViteStatic.chunk_by_key("src/entry1.js");
    dbg!(entry1);
}

// To see difference:
//
// ```shell
// cargo expand --example dynamic           # debug build (no chunks embedded)
// cargo expand --example dynamic --release # release build (chunks are embedded)
// ```