[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

• [x] Framework Core #15139
• [ ] Documentation
• [x] UI Components
• [x] Tooling

Documentation

• [x] Introduction
• [ ] Getting started
• [ ] Features
• [ ] Styles and animations
• [ ] Directives
• [ ] Resources
• [x] About

Tooling

• [x] CLI plugin
• [x] Vite plugin
• [x] Presets
• [x] 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

• [x] v-alert #14971
• [x] v-app #15179
• [x] v-app-bar #15192
• [x] v-autocomplete #15355
• [x] v-avatar #15112
• [x] v-badge #15193
• [x] v-banner #15109
• [x] v-bottom-navigation #15194
• [x] v-breadcrumbs #15181
• [x] v-btn #15213
• [x] v-btn-group #15195
• [x] v-btn-toggle #15196
• [x] v-card #15283
• [x] v-carousel #15197
• [x] v-checkbox #15264
• [x] v-chip #14973
• [x] v-chip-group #15198
• [x] v-code #15182
• [x] v-color-picker #15292
• [x] v-combobox #15354
• [x] v-counter #15183
• [x] v-default-provider
• [x] v-dialog #15289
• [x] v-divider #15113
• [x] v-expansion-panels #15295
• [x] v-field #15251
• [x] v-file-input #15288
• [x] v-footer #15114
• [x] v-form #15253
• [x] v-grid #15296
• [x] v-hover
• [x] v-icon #15212
• [x] v-img #15287
• [x] v-input #15260
• [x] v-kbd #15199
• [x] v-label #15256
• [x] v-lazy #15184
• [x] v-list #15360
• [x] v-locale-provider #15255
• [x] v-main #15254
• [x] v-menu 5e4992ffa
• [x] v-messages #15200
• [x] v-navigation-drawer #15263
• [x] v-no-ssr #15185
• [x] v-overlay #15284
• [x] v-pagination #15286
• [x] v-parallax #15226
• [x] v-progress-circular #15266
• [x] v-progress-linear #15265
• [x] v-radio #15258
• [x] v-radio-group #15259
• [x] v-range-slider #15228
• [x] v-rating #15285
• [x] v-responsive #15249
• [x] v-selection-control #15246
• [x] v-selection-control-group #15250
• [x] v-sheet #15115
• [x] v-slide-group #15248
• [x] v-slider #15227
• [x] v-snackbar #15242
• [x] v-switch #15247
• [x] v-system-bar #15243
• [x] v-table #15186
• [x] v-tabs #15262
• [x] v-text-field #15252
• [x] v-textarea #15257
• [x] v-theme-provider
• [x] v-timeline #15230
• [x] v-toolbar #15154
• [x] v-tooltip #15245
• [x] v-validation
• [x] v-window #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: https://github.com/vuetifyjs/vuetify/issues/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: https://github.com/vuetifyjs/vuetify/issues/13479#issuecomment-1115233462

[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: https://github.com/vuetifyjs/vuetify/issues/14621#issuecomment-1016186592 https://github.com/nuxt-community/vuetify-module/issues/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? Он удален полностью или добавлен позже? Это была удивительная функция кнопки.

https://github.com/vuetifyjs/vuetify/issues/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.

[sinisarudan]

@MartinX3 I can't understand people needing to upgrade to a new version as soon as possible, even if it is Beta.

I see that you don't understand, but the point is if you start a new project, you DON'T want to start it in v.2.x and then to migrate it all to v.3.x. Take in mind that it is not only vuetify 3, but you are by being forced to use vuetify 2, forced to use vue 2 too! So it is pretty pretty painful enforcement!

Thus, developers and PMs are "enforced" and motivated to do additional work and workarounds etc to enable v.3 version working, then to have the enormous work later in migrating whole the project.

I hope that collaborators on Vuetify are aware of this too :)

[MartinX3]

@sinisarudan I see you prefer very much time and energy into complaining instead and also investing very much time and energy to do workarounds and extra stuff, just to use as soon as possible the newest not ready software. Weird people. I hope you won't become my employee.

smart people just use vue 2 with vuetify 2 and just add the composition-api package and use typescript. Also smart people know that according to the roadmap you can just wait for vue 2.7 and vuetify 2.7 to easily migrate your project on 3.x without much work. (I use vue/vuetify as frontend for customers and also nuxtjs for (static) websites)

If you are so much into using vue/tify) 3 now go and pay for a support contract, go and donate, go and develop pull requests to accelerate the development of vue(tify) 3 or stop complaining.

[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?

[abumalekFayed]

In vuetify 3 documentation roadmap current release is alpha please correct this to avoide misconsiption .

[MartinX3]

?

[abumalekFayed]

i mean in this link https://next.vuetifyjs.com/en/introduction/roadmap/

[MartinX3]

This is BETA documentation for Vuetify 3, examples and information may be broken or outdated.

[AndreyYolkin]

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?

It's not listed in checklist, so we need to wait for 3.1

[eliezerp3]

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