Repository navigation
feat: build with the shared @pollora/vite-config - #4
Merged
Merged
Conversation
Same build and hot file as before: manifests and built files compared before and after, identical.
ogorzalka
marked this pull request as ready for review
October 8, 2026 10:08
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.
The Vite config moves into @pollora/vite-config (DDEV-aware dev server, hot file, block entries, Blade reload, theme.json for themes), a dev dependency like laravel-vite-plugin;
globis no longer needed.Verified: this template copied into a project layout, built before and after —
manifest.jsonand the list of built files are identical. Contract tests pass.Draft until
@pollora/vite-config1.0.0 is published on npm (CI cannot install it before).