RC 3.0.0 #200
Open
RC 3.0.0 #200
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
…yer approach (wip)
…inia and platformLanguages tests
✅ Deploy Preview for eager-jones-4cc84f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
- Add Vite optimizeDeps exclude configuration to fix #imports virtual import resolution issue - Move daisyui from devDependencies to dependencies for proper runtime availability - Add explanatory comment about Vite optimization exclusion necessity
- Add hook-based plugin override system that automatically filters out layer plugins when project has same-named plugins - Support both Nuxt 3 (plugins/) and Nuxt 4 (app/plugins/) directory structures for plugin overrides - Enhance platform languages loading to support both Nuxt 3 (locales/) and Nuxt 4 (app/locales/) directories - Update CSS path configuration to support relative paths for better layer inheritance - Improve file resolution with proper fallback chain for cross-version compatibility
- Fixed plugin override system to preserve original plugin execution order to prevent Pinia initialization issues - Changed from reordering plugins to in-place filtering to maintain framework plugin dependencies - Updated CSS path resolution to use layer alias (#layers/hubble/assets/css/tailwind.css) for proper override support
- Added automatic CSS loading that checks for consumer overrides in both Nuxt 3 (assets/) and Nuxt 4 (app/assets/) structures - Removed CSS from layer config since module now handles conditional loading dynamically - Fixed variable naming by reusing existing appDir variable to prevent conflicts - Prevents duplicate CSS loading while providing out-of-the-box styling with clean override pattern - Maintains backwards compatibility with existing consumer CSS setups
- Fixed CSS loading path resolution to handle both Nuxt 3 (relative "app") and Nuxt 4 compatibility mode (absolute path) - Applied same path resolution fix to platform languages loading - Added comprehensive comments explaining compatibilityVersion: 4 behavior changes - Ensures proper handling of nuxt.options.dir.app being absolute vs relative path This resolves issues where Nuxt 4 compatibility mode changes app directory from relative to absolute path, breaking CSS and platform languages file loading in the module.
- Improve plugin override system with better rootDir-based detection and alphabetical sorting - Add comprehensive CSS override pattern documentation with automatic loading behavior - Add troubleshooting sections for dynamic component resolution and mapping function overrides - Reorganize migration guide with step-by-step CSS migration instructions - Document how override systems work around Nuxt layer limitations for assets and plugins
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.