fix: Use import in vanilla-ts fragment.

[FabianLars]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Docs
• New Binding issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes, and the changes were approved in issue #___
• No

Checklist

• When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
• A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
• I have added a convincing reason for adding this feature, if necessary

Other information

[FabianLars]

And that's why you test changes locally before you open a PR 💃

[amrbashir]

What's the reason for this? This is a vanilla template so I think imports should be from the global tauri but I am fine with the change if there is a reasonable drive behind it.

[FabianLars]

Imo it just doesn't make sense to not use the npm package if vite (and typescript) is used, especially if we install the api package anyway.

[FabianLars]

Oh and the "trigger" for this PR was a help thread on discord where someone was confused why we use the global object in a typescript project https://discord.com/channels/616186924390023171/625037620996734986/1025553047436406835

[amrbashir]

Makes sense.

[amrbashir]

Can you also move the api package to normal dependencies section instead of dev?