chore(imports): update the imports declarations of type annotations and declarations to import type

[liby]

To be honest, when I was doing this PR, I saw a lot of related issues and pull.
e.g.:

• Type-only imports and exports
• Add option to disable TS using inline import types in quick fixes
• Feedback on 'import type' UX for editors
• Update type-only import semantics to allow type queries
• Type-only auto imports
• Auto import adds types to existing value imports under --importsNotUsedAsValues=error

Now I am beginning to think, is this really necessary?

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/pmndrs/jotai/FRyxyWfEzW433iqM1LFQd4FrPdrB
✅ Preview: https://jotai-git-fork-liby-master-pmndrs.vercel.app

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 1e36c08:

Sandbox	Source
React	Configuration
React Typescript	Configuration

[dai-shi]

is this really necessary?

This would be just a preference, but it helps to me to understand dependencies across bundles. So, it might not be really necessary, but make things consistent.

[dai-shi]

I also confirmed, tsconfig change doesn't affect bundles.

$ git diff tsconfig.json
diff --git a/tsconfig.json b/tsconfig.json
index 9f5dd48..3f3d107 100644
--- a/tsconfig.json
+++ b/tsconfig.json
@@ -2,7 +2,7 @@
   "compilerOptions": {
     "target": "es2019",
     "strict": true,
-    "jsx": "preserve",
+    "jsx": "react-jsx",
     "allowSyntheticDefaultImports": true,
     "esModuleInterop": true,
     "moduleResolution": "node",
$ diff -r dist.jsx_preserve dist.jsx_react-jsx
$ 

[dai-shi]

Thanks for the work. Much appreciated.
Yeah, it's not 100% certain if we can continue the style in the future.
For now, it looks good to me. (examples may not work with old TS, but let's hope no one complain.)

[liby]

This would be just a preference, but it helps to me to understand dependencies across bundles. So, it might not be really necessary, but make things consistent.

I see what you mean.

Thanks for the work. Much appreciated.

That's alright, glad to help!

For now, it looks good to me. (examples may not work with old TS, but let's hope no one complain.)

If there are any problems in the future, let's communicate at that time to see how to modify them.