"Failed to parse version `2` for crate `tauri`" - fresh install compile errors

[AMDphreak]

Fresh install compile errors:

PS Z:\code\amdphreak\bookmark-cleaner-ai\tauri-example> pnpm tauri dev

> tauri-example@0.1.0 tauri Z:\code\amdphreak\bookmark-cleaner-ai\tauri-example
> tauri "dev"

     Running BeforeDevCommand (`pnpm dev`)
       Error Failed to parse version `2` for crate `tauri`
       Error Failed to parse version `2` for crate `tauri-plugin-opener`
...

[AMDphreak]

Those need to be ^2 not 2 to stop triggering error.

How do you guys make that kind of mistake in your own starter template?

[FabianLars]

Our templates are correct but thanks for the attitude.

• "2" is a valid version specifier in cargo.toml which means that if users manually add more plugins, they will likely hit the same issue.
• The actual issue should be in the relatively recently added version checker here https://github.com/tauri-apps/tauri/blob/dev/crates/tauri-cli/src/info/plugins.rs
• it's not a compile error / hard error. this has close to no actual consequences. This of course does not mean that we shouldn't fix the problem!

[AMDphreak]

It was the cargo.toml file. I assumed it was some other templates matching a "^2" substring search. changing version to "^2" worked -- doesn't even need the ^2.0.0.

Our templates are correct but thanks for the attitude.

• "2" is a valid version specifier in cargo.toml which means that if users manually add more plugins, they will likely hit the same issue.
• The actual issue should be in the relatively recently added version checker here https://github.com/tauri-apps/tauri/blob/dev/crates/tauri-cli/src/info/plugins.rs
• it's not a compile error / hard error. this has close to no actual consequences. This of course does not mean that we shouldn't fix the problem!

If that's the case, well, fine, but why is it working when I change to ^2? Confusing.

[FabianLars]

If that's the case, well, fine, but why is it working when I change to ^2? Confusing.

I assume it's actually because that caused the Cargo.lock file to build. If you change it to ^2 and delete Cargo.lock, it should throw the same error again - just with ^2 instead of 2 in the message.

https://docs.rs/semver/latest/semver/struct.Version.html has pretty strict requirements but we're simply using it wrong. It's fine when we can pull the versions from the lockfile but Cargo.toml lists version requirements not the actual versions (unless locked at patch level i guess). I think i'll change the linked code to simply not print errors when falling back to reading Cargo.toml since there's not much value in comparing version requirements if we don't know what they will resolve to.