feat!: jiti support#1460
Conversation
Thanks for all the PRs 🚀
There might be an open issue, but I'm not so sure about it. Either the consumers are having a modern
I updated some protection rules in other repos, but not in this one 🤔 also checked it again and nothing changed that would block creation of branch that are not named |
Shinigami92
added
breaking change
Might be something in the org since I can't assign, add tags or close issues too. Now I'll take a look on the typescript related issues to check what is fixed or if I'm missing something. #1397 docs not needed, jiti will detect bun and use its runtime. 
#907 I think that this one is already fixed since I can't reproduce, same to docker #1184 (both are working on the latest |
|
@brenoepics would it be okay for you to extract the doc/vitepress changes into a separate PR? |
Co-authored-by: Shinigami <chrissi92@hotmail.de>
2 participants
Added jiti support along with a few tests to ensure we can load all supported
.js,.ts, etc.Also, should we add
.mjsand.mtsto the create migration command? it works fine with jiti.Leaving this as a draft for now I still need to remove thets-node,babel, and other related flags, and update the docs.EDIT: finally it worked, for some reason I couldn't make a new branch so I created a fork and made the PR