Seperate type imports and class imports for typescript client binding… #2787
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Seperate type imports and class imports for typescript client bindings codegen
Description of Changes
Currently the code generation works fine following the typescript client setup tutorial in the documentation if you select Typescript+SWC as the variant in the vite template menu



However if you select typescript only, the bindings generated by spacetimedb will not be bundled correctly by vite. This is described in vite's documentation here:
The end result is a client side error of trying to import a type from a JS file:
This fix separates the type imports from the class imports in the generated typescript code, turning:
into
solving the problem.
Relevant issues
#3024
#2661
API and ABI breaking changes
This is not a breaking change
Expected complexity level and risk
1
Testing