Funnily enough I am using it in a Vite application right now, it took a little bit of fiddling but wasn't too difficult (and will be made into a plugin soon).
As the library is coupled with typescript there must be some build tool involved to turn it into javascript. The real problem I have is a severe lack of reflection tools for both javascript and typescript. It was what forced me down the babel path in the first place!
Saying that, you can use it with no build tools at all, you just lose the "magic" type inference powers.
encase is only one way to skin an ICat 😄 there's also a useResolve hook that lets you write more "traditional" hooks:
Thanks for the feedback!
Funnily enough I am using it in a Vite application right now, it took a little bit of fiddling but wasn't too difficult (and will be made into a plugin soon).
As the library is coupled with typescript there must be some build tool involved to turn it into javascript. The real problem I have is a severe lack of reflection tools for both javascript and typescript. It was what forced me down the babel path in the first place!
Saying that, you can use it with no build tools at all, you just lose the "magic" type inference powers.
encase
is only one way to skin anICat
😄 there's also auseResolve
hook that lets you write more "traditional" hooks:I definitely should've made that clear in this post.