fix(api): add type definitions to package.json exports

[ankoh]

This commit includes the typescript type definitions in the package exports of @tauri-apps/api.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/svelte-check@2.9.2	Transitive: filesystem, unsafe	+7	4.6 MB	svelte-language-tools-deploy
npm/svelte-preprocess@4.10.7	environment, filesystem Transitive: eval	+20	4.94 MB	dummdidumm
npm/svelte@3.52.0	None	0	8.93 MB	conduitry
npm/tslib@2.4.1	None	0	52.8 kB	typescript-bot
npm/typescript@4.8.4	None	0	68.8 MB	typescript-bot
npm/vite-plugin-static-copy@0.11.1	environment, filesystem	+3	155 kB	sapphi-red
npm/vite-plugin-top-level-await@1.2.1	unsafe Transitive: environment, filesystem, shell	+11	677 MB	menci
npm/vite-plugin-wasm@3.1.0	filesystem, network	0	16.2 kB	menci
npm/vite@3.2.2	environment, eval, filesystem, network, shell, unsafe	+7	3.79 MB	vitebot

🚮 Removed packages: npm/type-check@0.4.0, npm/typescript@5.3.3, npm/which-typed-array@1.1.13

View full report↗︎

[ankoh]

Without this commit, tsc will just fail to resolve the type definitions in some cases (for me it occurred with NodeNext module resolution through ts-jest)

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Install scripts	npm/svelte-preprocess@4.10.7	Install script: postinstall Source: echo "[svelte-preprocess] Don't forget to install the preprocessors packages that will be used: node-sass/sass, stylus, less, postcss & postcss-load-config, coffeescript, pug, etc..."	examples/web/package.json

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/svelte-preprocess@4.10.7