Open
Conversation
…lining, bump dependencies
The tip regarding automatic disabling of inline styles when SSR is enabled was specific to version v0.18.0. This information is no longer accurate or necessary for current users.
- Add vuetify to the workspace catalog to manage version centrally - Update playground and vuetify-nuxt-module to use catalog version - Bump vuetify from 4.0.0 to 4.0.1 - Update related dependencies in lockfile
Add layers.css to define custom CSS layer order and app.css for custom styles. Include both files in Nuxt config to apply them globally.
…lities Conditionally load the new modular styles (core, utilities, colors) for Vuetify 4.0.0 and above, while maintaining backward compatibility. This ensures the module works correctly with the updated Vuetify 4 styles structure.
…in dev Enable caching for processed Vuetify SCSS files during development to improve rebuild performance. The cache is automatically invalidated when relevant SASS/SCSS files change.
Contributor
Author
|
/publish |
commit: |
|
woah, this is absolutely massive 🙏 |
Member
|
It should be cool to add unocss-preset and tw-preset playground to compare DX experience (initial dev server css styles) and build size (CSS) |
Improve readability by reorganizing the installation instructions into "New Project" and "Existing Project" sections. Replace the warning block with a clearer compatibility table and version history details. Add code groups for different package managers to enhance user experience.
Set the logo to a new horizontal SVG file and add CSS rules to properly space the logo within the navigation bar. Also adjust the CSS variable for the navigation logo height to match the new asset.
Update links in the documentation index page to reflect the new organized guide structure, ensuring users can navigate to the correct sections
|
quick question : will we get a migration guide or will the release notes be enough for us to figure out the changes to make ? |
Contributor
Author
|
Think of v1 as of finalizing all the work was done before. Besides removal of |
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
3 participants
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
Linked Issues
Closes #352 #346 #350
Refactor repo aiming to release v1.0.0
disableVuetifyStyleswas removed, usestyles: 'none'insteadAdditional Context
Tip
The author of this PR can publish a preview release by commenting
/publishbelow.