Switching to Bun for dev #783
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Switches to Bun
This PR switches to using Bun as the development runtime. This is an experiment; however, it's way, WAY faster to run. Like 20x+ faster in my tests.
Gluegun will continue to work in Node-powered CLIs (and we need to do extensive testing to ensure that is the case). Over time, the gap between the two runtimes will converge. And, if it works well enough, we will recommend that others use Bun instead of Node.
Running this with Bun would mean doing something like this:
Jarred said that they're looking to make this better. https://twitter.com/jarredsumner/status/1702840231584743485
You can also run
bunx gluegun-bun ...(theoretically), and locally you can link it withbun linkand thengluegun-bun ...to force using bun.Removes the ability to generate JS (non-TypeScript) CLIs using
gluegun newThis has been a long time coming. The reasons for removing the JS-only template are that we do not use Gluegun to build CLIs without TypeScript anymore and this also simplifies the template quite a bit.
Yes, I could make this a separate PR. Why do you ask? 😅