[Task] Vuetify 3 Release Checklist

[johnleider]

V3 Release Checklist

The following is an in progress list of remaining tasks before we release the next version.

This will be updated daily; so watch for changes.

Discord, https://community.vuetifyjs.com/ and join channel #v3-discussion.

Final review

• Framework Core refactor(framework): tuning pass #15139
• Documentation
• UI Components
• Tooling

Documentation

• Introduction
• Getting started
• Features
• Styles and animations
• Directives
• Resources
• About

Tooling

• CLI plugin
• Vite plugin
• Presets
• Eslint

UI Components

A component is considered complete when the following criteria is met:

• Primary and child components reviewed
  • imports ordered with appropriate comments
  • converted to use grid css structure (if applicable)
  • unit tests
    • jest spec test (if applicable)
    • cypress e2e test
• SASS/SCSS code reviewed
  • removes deprecated or unused code
  • abstracted explicit values to variables
  • verified sass variable usage
• index.ts file export formatted
• Documentation page
  • all examples working with no deprecated code
  • removed unused or deprecated examples
  • added all components page image
  • added quick bar and links
  • updated page entry and formatting
  • new sections added
    • accessibility (if applicable)
    • anatomy
    • grid (if applicable)
    • sass variables
    • theme (if applicable)
  • updated api section formatting
  • frontmatter information reviewed

• v-alert refactor(VAlert): tuning pass #14971
• v-app refactor(VApp): tuning pass #15179
• v-app-bar refactor(VAppBar): tuning pass #15192
• v-autocomplete refactor(VAutocomplete): tuning pass #15355
• v-avatar refactor(VAvatar): tuning pass #15112
• v-badge refactor(VBadge): tuning pass #15193
• v-banner refactor(VBanner): tuning pass #15109
• v-bottom-navigation refactor(VBottomNavigation): tuning pass #15194
• v-breadcrumbs refactor(VBreadcrumbs): tuning pass #15181
• v-btn refactor(VBtn): tuning pass #15213
• v-btn-group refactor(VBtnGroup): tuning pass #15195
• v-btn-toggle refactor(VBtnToggle): tuning pass #15196
• v-card refactor(VCard): tuning pass #15283
• v-carousel refactor(VCarousel): tuning pass #15197
• v-checkbox refactor(VCheckbox): tuning pass #15264
• v-chip refactor(VChip): tuning pass #14973
• v-chip-group refactor(VChipGroup): tuning pass #15198
• v-code refactor(VCode): tuning pass #15182
• v-color-picker refactor(VColorPicker): tuning pass #15292
• v-combobox refactor(VCombobox): tuning pass #15354
• v-counter refactor(VCounter): tuning pass #15183
• v-default-provider
• v-dialog refactor(VDialog): tuning pass #15289
• v-divider refactor(VDivider): tuning pass #15113
• v-expansion-panels refactor(VExpansionPanels): tuning pass #15295
• v-field refactor(VField): tuning pass #15251
• v-file-input refactor(VFileInput): tuning pass #15288
• v-footer refactor(VFooter): tuning pass #15114
• v-form refactor(VForm): tuning pass #15253
• v-grid refactor(VGrid): tuning pass #15296
• v-hover
• v-icon refactor(VIcon): tuning pass #15212
• v-img refactor(VImg): tuning pass #15287
• v-input refactor(VInput): tuning pass #15260
• v-kbd refactor(VKbd): tuning pass #15199
• v-label refactor(VLabel): tuning pass #15256
• v-lazy refactor(VLazy): tuning pass #15184
• v-list refactor(VList): tuning pass #15360
• v-locale-provider refactor(VLocaleProvider): tuning pass #15255
• v-main refactor(VMain): tuning pass #15254
• v-menu 5e4992f
• v-messages refactor(VMessages): tuning pass #15200
• v-navigation-drawer refactor(VNavigationDrawer): tuning pass #15263
• v-no-ssr refactor(VNoSsr): tuning pass #15185
• v-overlay refactor(VOverlay): tuning pass #15284
• v-pagination refactor(VPagination): tuning pass #15286
• v-parallax refactor(VParallax): tuning pass #15226
• v-progress-circular refactor(VProgressCircular): tuning pass #15266
• v-progress-linear refactor(VProgressLinear): tuning pass #15265
• v-radio refactor(VRadio): tuning pass #15258
• v-radio-group refactor(VRadioGroup): tuning pass #15259
• v-range-slider refactor(VRangeSlider): tuning pass #15228
• v-rating refactor(VRating): tuning pass #15285
• v-responsive refactor(VResponsive): tuning pass #15249
• v-selection-control refactor(VSelectionControl): tuning pass #15246
• v-selection-control-group refactor(VSelectionControlGroup): tuning pass #15250
• v-sheet refactor(VSheet): tuning pass #15115
• v-slide-group refactor(VSlideGroup): tuning pass #15248
• v-slider refactor(VSlider): tuning pass #15227
• v-snackbar refactor(VSnackbar): tuning pass #15242
• v-switch refactor(VSwitch): tuning pass #15247
• v-system-bar refactor(VSystemBar): tuning pass #15243
• v-table refactor(VTable): tuning pass #15186
• v-tabs refactor(VTabs): tuning pass #15262
• v-text-field refactor(VTextField): tuning pass #15252
• v-textarea refactor(VTextarea): tuning pass #15257
• v-theme-provider
• v-timeline refactor(VTimeline): tuning pass #15230
• v-toolbar refactor(VToolbar): tuning pass #15154
• v-tooltip refactor(VTooltip): tuning pass #15245
• v-validation
• v-window refactor(VWindow): tuning pass #15244

[michaelnguyen08]

I'm sorry, v-time-picker and v-date-picker not coming with this release?

[omerkimel]

What about v-data-table?

[JesusFregoso]

What about v-skeleton-loader ?

[gregveres]

@michaelnguyen08, @omerkimel , @JesusFregoso You can see the list of components that didn't make the 3.0 cut in the 3.1 milestone.

These were cut from the initial release fairly early this year. Noteably this includes the following components:

• Calendar
• TimePicker
• data-iterator
• date picker
• v-stepper
• v-speed-dial
• v-skeleton-loader
  There are some feature requests in the milestone that I am hoping John and the team will punt to a later release to expedite getting these base components released.

v-data-table was mentioned in above, but that is supposed to be in v3.0.0 milestone. I just looked at the docs for v3 and it looks like v-data-table was renamed to v-table. v-table is in the docs and in the list above so that appears to have made the cut for v3.0.

[AquaMCU]

Hi. I just opened the node_modules/vuetify/lib/components directory and I can see, that a component directory "VDataTable" is included in the Beta.1 build. When I try to include it in my App, I see, that VUE is not able to resolve it "[Vue warn]: Failed to resolve component: v-data-table". Seems, that the component is just not registered.

And I disagree, that will be renamed...

[MajesticPotatoe]

Hi. I just opened the node_modules/vuetify/lib/components directory and I can see, that a component directory "VDataTable" is included in the Beta.1 build. When I try to include it in my App, I see, that VUE is not able to resolve it "[Vue warn]: Failed to resolve component: v-data-table". Seems, that the component is just not registered.

Directory is still there because its not that it is being removed, it just hasn't been converted.
this: https://github.com/vuetifyjs/vuetify/blob/next/packages/vuetify/src/components/index.ts
controls what actually get exported and is what is currently available to use

[zorn-v]

Where is loading prop in VBtn component ?
Is it removed completely or added later ?
It was amazing button feature.

[aentwist]

I am guessing that not only are components being cut, but also props? For example, Menu is missing a fantastic amount of props functionality -

https://vuetifyjs.com/en/api/v-menu/#props
https://next.vuetifyjs.com/en/api/v-menu/#props

I need left 😕

What is the plan with this?

[warflash]

I am guessing that not only are components being cut, but also props? For example, Menu is missing a fantastic amount of props functionality -

https://vuetifyjs.com/en/api/v-menu/#props https://next.vuetifyjs.com/en/api/v-menu/#props

I need left 😕

What is the plan with this?

@aentwist
Well v-menu is still WIP, you can track the progress here: #13489 or in the 3.0.0 milestone

I need left 😕

I have not used v3 yet but based on the docs it seems like :anchor="start" could be what you are looking for?

[johnleider]

I am guessing that not only are components being cut, but also props? For example, Menu is missing a fantastic amount of props functionality -

https://vuetifyjs.com/en/api/v-menu/#props

https://next.vuetifyjs.com/en/api/v-menu/#props

I need left 😕

What is the plan with this?

I don't think we have any completely removed props. Some may have been combined to be more intuitive, but they are there.

In regards to v-btn, the v-progress-circular component wasn't ported when it was. It'll be there, I just have to get to it.

[aentwist]

I was imagining the combination of offset-y and left, which is now done with anchor="bottom end". Thanks for the tip with anchor, I missed that in the Menu docs. Thanks to both for the info about the props.

[Stevelriemenbill]

What about v-data-table?

see following answer for those interested: #13479 (comment)

[MatthewAry]

Would like to suggest adding a Nuxt3 plugin to this list as well.

[warflash]

Would like to suggest adding a Nuxt3 plugin to this list as well.

@MatthewAry
I'd love to see first class nuxt support as well, though that's something done by nuxt itself, not vuetify.
Related:
#14621 (comment)
nuxt-community/vuetify-module#475

[MatthewAry]

@warflash If that's what @KaelWD says then I suppose that's how it is. However I am really anxious to see support for SASS Variables in Nuxt3 for the Vuetify project.

[Azema4ka]

Где находится loadingподдержка в компоненте VBtn? Он удален полностью или добавлен позже? Это была удивительная функция кнопки.

#15056

[edmundmunday]

For those components not included in the initial release, is there an incremental path for people who's apps use those components, or are they just going to have to wait until 3.1 before they can upgrade?

[MartinX3]

Isn't
3.0
3.1
3.2
3.x
incremental enough?

Just wait until everything is proper released.
I can't understand people needing to upgrade to a new version as soon as possible, even if it is Beta.

The only thing I would like would be a comparison table about which component gets added into which version.

Also you can wait for Vue 2.7 and Vueitfy 2.7.
These are already announced migration versions with backported features.....

[gregveres]

For those components not included in the initial release, is there an incremental path for people who's apps use those components, or are they just going to have to wait until 3.1 before they can upgrade?

If you rely on some of the components that aren't going to be in 3.0, I see two choices:

1. you wait until the release that contains all of the components you use
2. you replace the missing components with components you build

I have been waiting for Vuetify 3 so that I can migrate to Vue 3 and Vite, but I have chosen option 1 above. I use most of the components that aren't available in 3.0

• Data Table
• Calendar
• TimePicker
• date picker
• v-stepper
• v-skeleton-loader

[websitevirtuoso]

Please add v-data-table in this release. Thanks

[johnleider]

Please add v-data-table in this release. Thanks

How? It's not done.

[km2442]

I am not sure of anything anymore, I have read a lot of contradictory information... Will v-data-table be available in 3.0 or do I have to wait for 3.1?

[quiquelhappy]

Target release is this month. Is this checklist actually only 1/90 or have they just not been updating it?

I'm also interested on the update progress. No hurries, it will be ready when its ready, but it would be nice to have an eta, even if it is a bit vague. Best of luck to the contributors helping accelerate the update. No pressure at all!

[zorn-v]

@Tan-Jerry after you submit PR's to accelerate porting.

@MartinX3 Did you try it by yourself ?
PR's does not accelerate anything. Just for example (prior bugs for me)
#15132
#15129

[johnleider]

Keep it civil please. We are going to get to everything, including community submitted PRs.

[sinisarudan]

Hmm, I was trying to keep bearing with Vuetify 3 (even implementing some workarounds on our ongoing projects) until target release is here.
Yet:

• official deadline for Vuetify Target release has passed (May) but we're still in Beta
• there are no answers from developers regarding not-working functionality even the one documented in Beta as working Behaviour of Beta components doesn't follow official Beta docs? #15054
• we do not get updates when something is going to be delivered, after the self-defined deadlined has passed, so we can hardly make valid decisions
• as some of you mentioned here, it seems that the TARGET release of 3.0 (expected in the passed May) won't be a "real" target release in sense it will still lack too many components of their functionality, compared to 2.x version ...
• I would like to hear some opposing reassuring thoughts from developers, yet it seems that the waiting and workarounds inspired by "too optimistic" announcements by Vuetify developers is not justified anymore :(
• Especially that this is not ony waiting for Vuetify 3 but also preventing us from switching from Vue2 to Vue 3 and all the new ecosystem being built around it (so waiting on 2.7 and suggested (automatic) migration to 3.x using it is neither solution, esp. that it has also been prolonged for several months)

In another thread #14776 the Quasar is mentioned as an alternative while we wait for the Vuetify 3 reaching that level of stability and versatility. I guess I will give it a try.

P.S. Dear @MartinX3 please keep it civil, multiple developers here get "attacked" by you for having different opinions. It's ok to have different opinions even calls for action, and by aggressive reactions to someones opinions we even get stronger reactions and fortify them in the opinions we might not like :)

Best wishes to Vuetify team and keep your good work, we all, by being developers, know how it is to work under pressure and we should have empathy.

On the other side we also have our own dependent projects and our clients/bosses above our heads, and it would help both us and you I guess to be more transparent and objective regarding releases so that we can make our decisions on time and to avoid disappointments.

The main info missing and being misleading as I see by reading community questions is on which date approximately or which release we should expect that we have let's say 90% of the components/functionality provided in 2.x versions

Thanks, best!

[KaelWD]

• They're estimates not deadlines.
• I don't have a link but that's been answered before, documentation is obviously one of the last things to be updated.
• We don't know either.
• etc.

90% of the components/functionality provided in 2.x versions

I'd say we're pretty close, the only components missing are the big complex ones that depend on other functionality being stable:

• treeview (in progress)
• data table (in progress)
• calendar (in progress)
• pickers (in progress)

[sinisarudan]

thanks for the update @KaelWD , we're getting closer to some estimates.

Regarding DOCS, I'm not telling that the Docs are not updated.
On the contrary! The v.3.0 docs for v-select state that props-item are working as expected.

Yet as I and other devs have stated, read more here in the explained issue - that's not the fact. I myself tried to test it even beyond docs in different ways..

The problem here is that we lose the point of reference/truth, on what can we rely in the current beta.1 and the following versions of Vuetify?

Or you're trying to say that the docs DOES NOT reflect the currently released version and is written independently to reflect the final (desired) v.3.0?

If it does reflect, could anyone investigate that issue of v-select. As being one of the central UX components and not working as documented, I feel we are pushed for alternatives.

Thanks in andvance

[KaelWD]

You might've missed this

The example you linked to was for v2 and hasn't been updated yet, it needs item-title="text" to work with those objects

[MatthewAry]

Here is my unsolicited feedback on this recent tangent, I think others might find it useful. Note: I am making assumptions about the state of things in this project so if I am wrong please feel free to correct me.

@sinisarudan Vuetify 3 is beta, which usually means:

• Development has priority over authoring docs right now.
• Errata, and missing information is to be expected in the docs while in beta up until V3 reaches some unspecified level of maturity.
• The development team has no obligation to provide API guarantees until GA.
• The scope of the V3 initial release is locked in, what you see on the release checklist is meant to give you an idea how close/far they are to release.
• I have my own questions about V3 but I know that it would be inappropriate to ask them HOW to do something with V3 Beta, and more appropriate to ask them if a specific feature, or component will be included in the initial release (excluding anything that they may consider obvious)
• The dev team is free to ignore discussions or bug reports until V3 is released. They are more likely to interact with you if you intend to contribute code or if you engage with them on something that team members are currently concerned with or occupied with.

I specifically posted to this task, because I wanted to know about a feature. I didn't get a response, and it's no big deal for me right now. I have other things to worry about.

TLDR: Don't expect any kind of support from the dev team for non GA releases. They're still making V3 and will more likely converse with you as long as the discussion has to do with any of their present concerns.

[johnleider]

I feel like I shouldn't have to say this since it is plastered on every page of the next docs, but alas:

[MartinX3]

Please learn how to read and stop spamming the Vuetify 3.0 Release CHECKLIST issue ticket.

I didn't subscribe it to read wining people screaming for ETA without really helping the project and ignoring text warnings.

[johnleider]

Would like to suggest adding a Nuxt3 plugin to this list as well.

I will need help with this as I do not use NUXT. Happy to help however I can though.