You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With doubling-down down on a plugin approach (Issue for context: #6339, RFC coming soon from @lucasfernog) there are going to be more and more packages to deal with in the Tauri ecosystem. A lot (all?) of them will require the user performing the following steps:
Add to Cargo
Add to Node (if using)
Register the plugin in main.rs
Then you can begin using the plugin via imports
This is a lot of steps just to start using something like the upcoming camera plugin and can cause a lot of friction to the DX of Tauri.
Analysing the project (determine if it's only Rust, if there's a node project, if pnpm, etc.)
Propose the changes visually with diffs in the terminal for the user to make (such as adding the dependencies, updating main.rs, etc.)
Applying those changes on the user's confirmation
Alternatives considered
No response
Additional context
This can become quite tricky when dealing with different package versions across the Tauri ecosystem. We may need to have a conversation around what versions and compatibility between versions looks like. I may put in an RFC after this week's WG call to begin this discussion.
Future considerations
We may want to look at expanding this to handle adding frontend frameworks (Svelte, Vue, etc.) but that is a lot more complicated. I'd take this as a first step and see where we land.
The text was updated successfully, but these errors were encountered:
Describe the problem
With doubling-down down on a plugin approach (Issue for context: #6339, RFC coming soon from @lucasfernog) there are going to be more and more packages to deal with in the Tauri ecosystem. A lot (all?) of them will require the user performing the following steps:
main.rs
This is a lot of steps just to start using something like the upcoming
camera
plugin and can cause a lot of friction to the DX of Tauri.Describe the solution you'd like
I'd propose adding a command to the Tauri CLI:
tauri add
. The inspiration from this is the way Astro handles their integration ecosystem: https://docs.astro.build/en/guides/integrations-guide/#automatic-integration-setupsvelte-add
is another example of this: https://github.com/svelte-add/svelte-addThis could allow you to do something like this:
That would complete steps 1-3 for your by...
main.rs
, etc.)Alternatives considered
No response
Additional context
This can become quite tricky when dealing with different package versions across the Tauri ecosystem. We may need to have a conversation around what versions and compatibility between versions looks like. I may put in an RFC after this week's WG call to begin this discussion.
Future considerations
We may want to look at expanding this to handle adding frontend frameworks (Svelte, Vue, etc.) but that is a lot more complicated. I'd take this as a first step and see where we land.
The text was updated successfully, but these errors were encountered: