generated files contain timestamp

[AlphaLiu]

Module

ts (vanilla TypeScript generation)

Description

Hi,

Every time the run dev, it regenerates files even if no content related to the files that need generation has been modified. Moreover, the generated files always contain a timestamp, which updates every time the program runs.​

Git will judge the files as modified solely due to the timestamp change, resulting in frequent meaningless changes in the workspace and increasing the cost of filtering commits.​

Expected Improvements​

Do not regenerate files when there are no content changes;​
Or provide an option to make the generated files exclude dynamic timestamps.

Thank you.

[thwbh]

Hi, thank you for your report, the behavior you want is actually supposed to work. I wasn't aware of that being broken because in my projects, the generated sources folders are ignored via .gitignore and they always get rebuilt for production during CI/CD. I'll look into it.

[AlphaLiu]

Hi there,
Thanks a lot for your prompt reply ! It totally makes sense that ignoring the generated sources folders via .gitignore can bypass the git change detection issue caused by the timestamp updates. If these generated files don’t need to be tracked in version control, the current behavior is perfectly workable.

[thwbh]

I just revisited the implementation and realized the caching never found its way into the codebase. Whoops.

How it should work:

• codegen creates a .tauri-typegen-cache file containing a checksum
• if the project setup is configured to automatically regenerate on cargo check or cargo build, the codegen should only run if the new checksum does not match

ast_cache.rs L14 already has a modified field but it's commented out.

/// Cache entry for a parsed Rust file
#[derive(Debug, Clone)]
pub struct ParsedFile {
    /// The parsed AST
    pub ast: SynFile,
    /// File path for reference
    pub path: PathBuf,
    // Last modified time for cache invalidation (if needed later)
    // modified: std::time::SystemTime,
}

Lastly, I need to add a readme section suggesting putting the whole codegen folder to .gitignore and to provide a hint towards preventing the dev server looping on accidental changes of those files (e.g. formatting through the IDE) when the folder is not part of .taurignore.

[thwbh]

The generator will now tell you when there's no regeneration performed. Example

cargo tauri-typegen generate --verbose

...
✅ Analyzing Tauri commands - Found 13 commands
🔄 Changes detected, regenerating bindings
🚀 Generating TypeScript bindings (4/4)
✅ Generating TypeScript bindings - Generated 4 files
✓ Generation complete
...

Running the same command again:

...
✅ Analyzing Tauri commands - Found 13 commands
✨ Cache hit - no changes detected, skipping generation
✅ TypeScript bindings are up to date
...

You can force regeneration regardless with the --force flag.

cargo tauri-typegen generate --verbose --force

...
✅ Analyzing Tauri commands - Found 13 commands
🔄 Force flag set, regenerating bindings
🚀 Generating TypeScript bindings (4/4)
✅ Generating TypeScript bindings - Generated 4 files
✓ Generation complete
...

The force property was added to the config and will be overruled during manual CLI execution.

[thwbh]

fixed in 0.4.1