fix: handle array-returning Vite plugins in mergeConfigDedup #89
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.
Description
mergeConfigDedupassumed every entry in thepluginsarray is a singlePluginobject with a.nameproperty. However, Vite'sPluginOptiontype allows plugins to be arrays (nested), falsy values, or promises. Plugins like@tailwindcss/vitereturnPlugin[]— a standard Vite convention called "plugin presets." This causedmergeConfigDedupto fail because it accessed.nameon an array.FIXES
@tailwindcss/viteand similar)false,null,undefined) — standard Vite convention for conditional plugins.nameworks correctly for all plugin typesTest Plan
Added unit tests in
packages/appkit/src/utils/tests/vite-config-merge.test.tscovering:Manual Testing
appkitto make sure this fixed the issue