fix: Incorrect types export

[lukmccall]

Exporting a type without annotation (not using export type) can cause some unexpected bugs. For example, when using tools like rnx-kit with tree shaking enabled, the project may fail to compile because it tries to import a non-existing type. During the tree shaking step, those types are removed, so using correct export annotations can help avoid these issues.

[alexbrazier]

I actually reverted this change a while ago due to it causing import errors for some people #17 #16

I'm assuming this will bring back those issues again?

[lukmccall]

Hello @alexbrazier, thank you for your response! AFAIK, the bundler should load the compiled JavaScript file instead of the source folder. In the linked issue, it seems like Metro is attempting to use the .ts file for some unknown reason. I'm not sure if your package was built before it was published four years ago. Still, currently, you are publishing compiled JavaScript files that shouldn't contain any information regarding exported types, at least not in .js files.

[alexbrazier]

Looks like it should be fine and there seem to be some other type exports in the project so happy to try it