fix: #1512

[Laegel]

What kind of change does this PR introduce? (check at least one)

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

Does this PR introduce a breaking change? (check one)

• Yes. Issue Cannot import @tauri-apps/api/tauri #1512
• No

The PR fulfills these requirements:

• When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:
I've made my tests by running and publishing to a local Verdaccio.

How the package looks like in node_modules:

An extract of my code (made with an old Vue CLI and Vue 2):

Hovering the invoke function displays the types as expected:

Result browser-side:

With the Compotes project (see #1512):

[nothingismagick]

Question: is there ever a reason for us to ship the TS?

[Laegel]

Question: is there ever a reason for us to ship the TS?

Not really, that's why we only have type definitions. :)

[nothingismagick]

But lets merge and release