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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
taco-api@3.0.0
Major Changes
65ccf6d: replace express with elysia.
Taco API now runs on top of bun and we have faster and better HTTP frameworks.
We don't do anything fancy that only express could do. To provide an HTTP client for a single endpoint, we can rely on something more modern.
bc854f6: Switch from node to bun
In case you don't know bun, I strongly recommend you to take a look in their docs. In summary, it's a fast JavaScript runtime that provides tons of performance and great nodejs compat.
The advantage of using Bun instead Node is:
tsx
for handling TypeScript files (such as scripts) or running the dev locally;esbuild
to build the final file;pnpm
to install dependencies;Though, because we're using Prisma and it relies on NodeJS to do some generation, you may still have Node installed.
Some differences from the previous setup:
Install dependencies:
Run dev server:
Build the project:
etc..
Because we're changing the runner, it's a major bump. If you still want to use Node, I'd recommend you to be in the version 2.
5384de3: new docs website.
Now, instead using vuepress, I've switch to starlight and refactor the whole docs.