fix: trigger patch release for production build fix - #6
Merged
Conversation
The plugin was consuming 90% of build time during `vite build` because Rolldown called into the transform hook for every module. Using Vite's `apply: "serve"` option removes the plugin entirely from the build pipeline in production, eliminating all hook call overhead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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.
Summary
Empty commit with conventional commit message (
fix:prefix) to trigger semantic-release for the production build fix merged in #5.The previous PR's squash-merge commit didn't use conventional commit format, so semantic-release skipped publishing.
What gets released
The
apply: "serve"fix from #5 — eliminates the 90% build time overhead from solid-grab duringvite build.