Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(deps): update dependency vuetify to v3 #192

Closed
wants to merge 2 commits into from
Closed

fix(deps): update dependency vuetify to v3 #192

wants to merge 2 commits into from

Conversation

BacLuc
Copy link
Owner

@BacLuc BacLuc commented May 16, 2023

This PR contains the following updates:

Package Type Update Change
vuetify (source) dependencies major 2.6.15 -> 3.2.5

Release Notes

vuetifyjs/vuetify

v3.2.5

Compare Source

🔧 Bug Fixes

v3.2.4

Compare Source

🔧 Bug Fixes
🔬 Code Refactoring
  • framework: use shallowRef instead of ref for primitives (#​17316) (04c9699)
  • VAlert: normalize text slot and prop (49d44fa)

v3.2.3

Compare Source

🔧 Bug Fixes
🧪 Labs
🔬 Code Refactoring
  • framework: convert all component props to factory functions (#​17263) (b5d725b)

v3.2.2

Compare Source

🔧 Bug Fixes
🔬 Code Refactoring
  • VBtn: explicitly define onClick function (633f0b1)

v3.2.1

Compare Source

🚀 Features
  • defaults: simplify useDefaults usage (9b7b7b9)

v3.2.0

Compare Source

v3.2.0 (Orion)

Welcome to the v3.2 release of Vuetify! The team has been hard at work on some exciting new updates and we're excited to finally get it into your hands!

Orion has a huge focus on improving the defaults engine and giving users more tools to customize their application. We started by adding support for global class and style defaults; then hooked it up to virtual components.

For example, you can set the default class for all v-btn components to be my-btn:

import { createVuetify } from 'vuetify'

export default createVuetify({
  defaults: {
    VBtn: {
      class: 'my-btn',
    },
  },
})

The same is possible for virtual components as well. Simply alias a core component and reference it by its name in the config object:

import { createVuetify } from 'vuetify'
import { VBtn } from 'vuetify/components/VBtn'

export default createVuetify({
  aliases: {
    MyBtn: VBtn,
  },

  defaults: {
    MyBtn: {
      color: 'primary',
      class: 'my-btn',
      variant: 'tonal',
    },
  },
})

Whenever you use the MyBtn component in any template it will be rendered as a v-btn with the default props applied:

<template>
  <my-btn>My Button</my-btn>
  <!-- <v-btn color="primary" variant="tonal" class="mt-btn">...</v-btn>-->
</template>

Finally, we made our defaults composable publicly available. Now you can hook your custom components into the defaults engine and configure your entire application from a single source.

<template>
  <div>
    I am {{ props.foo }}
  </div>
</template>

<script setup>
  import { useDefaults } from 'vuetify'

  const _props = defineProps({ foo: String })
  const props = useDefaults(_props)
</script>

defaults

The defaults composable also works with nested configurations. This works in any combination of virtual, custom, and core Vuetify components.

For example, you can create a custom component that modifies the default behavior of its children:

import { createVuetify } from 'vuetify'
import { VBtn } from 'vuetify/components/VBtn'
import { VCard } from 'vuetify/components/VCard'

export default createVuetify({
  aliases: {
    MyBtn: VBtn,
    MyCard: VCard,
  },

  defaults: {
    MyBtn: {
      color: 'primary',
      class: 'my-btn',
      variant: 'tonal',
    },
    MyCard: {
      border: true,
      variant: 'text',

      MyBtn: {
        color: 'secondary',
        variant: 'text',
      },
    },
  },
})

Some other big feature updates in this release include:

With v3.2 complete, the team is preparing for v2.7-lts (Nirvana) and the next v3 release, Icarus. We've recently updated our roadmap to be more transparent about our plans for the future; as well as improve the information about each release. Also, we've drastically improved the performance of the documentation and added new tools, such as 🎮Vuetify Play, to all component examples.

image

We hope that you enjoy this release as much as we have enjoyed working on it.

Until next time,

John Leider

💪 Support Vuetify Development

Vuetify is an open source MIT project that has been made possible due to the generous contributions by our sponsors and backers. If you are interested in supporting this project, please consider:

📖 Table of Contents

❗️ Important Links

📑 Upgrade guide

  • The title prop on v-tab is now text
  • The visible-items prop has been removed

💯 Release notes

🚀 Features
🔧 Bug Fixes
🧪 Labs
BREAKING CHANGES
  • VTab: The VTab title prop is now text
  • VVirtualScroll: visibleItems has been removed

🆘 I need help!

If you are stuck and need help, don't fret! We have a very large and dedicated community that is able to provide help 24/7. Come to the #vuetify-3-help channel.

v3.1.16

Compare Source

🔧 Bug Fixes
🔬 Code Refactoring
  • extract focusChild helper function (1646d67)
  • extract focusableChildren helper function (2531a83)
🧪 Labs

v3.1.15

Compare Source

🔧 Bug Fixes
🧪 Labs

v3.1.14

Compare Source

🔧 Bug Fixes
🧪 Labs

v3.1.13

Compare Source

This release may break some subcomponent defaults, for example VTabs > VSlideGroup should now just be set on VTabs instead.

🔧 Bug Fixes
🧪 Labs
🔬 Code Refactoring
  • defaults: skip merging deep if prev is undefined (c363981)
🔄 Reverts

v3.1.12

Compare Source

🔧 Bug Fixes
🧪 Labs
🔬 Code Refactoring
🔄 Reverts
  • Revert "fix(VDialog): position with transform instead of flex" (2bb27a9), closes #​16975

v3.1.11

Compare Source

🔧 Bug Fixes
🧪 Labs
🔬 Code Refactoring
  • replace explicit filter functions with options.filterProps() (d46caa9)
  • form: export interfaces used in createForm() (#​16894) (9532d7e)

v3.1.10

Compare Source

🔧 Bug Fixes
🔄 Reverts

v3.1.9

Compare Source

🔧 Bug Fixes
🔬 Code Refactoring

v3.1.8

Compare Source

🔧 Bug Fixes
🧪 Labs
🔬 Code Refactoring

v3.1.7

Compare Source

🔧 Bug Fixes
  • types: add volar compatible slot types (0fbdd0c)
  • VExpansionPanelTitle: add missing slot types (163ec60)
🧪 Labs

v3.1.6

Compare Source

🔧 Bug Fixes
🧪 Labs

v3.1.5

Compare Source

🔧 Bug Fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@BacLuc
Copy link
Owner Author

BacLuc commented May 16, 2023 •
edited
Loading

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: frontend/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: frontend@0.1.0
npm ERR! Found: vue@2.7.14
npm ERR! node_modules/vue
npm ERR!   vue@"2.7.14" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vue@"^3.2.0" from vuetify@3.2.5
npm ERR! node_modules/vuetify
npm ERR!   vuetify@"3.2.5" from the root project
npm ERR!   peer vuetify@"^3.0.0-beta.4" from vite-plugin-vuetify@1.0.2
npm ERR!   node_modules/vite-plugin-vuetify
npm ERR!     peerOptional vite-plugin-vuetify@"^1.0.0-alpha.12" from vuetify@3.2.5
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2023-05-16T10_38_00_056Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2023-05-16T10_38_00_056Z-debug-0.log

@BacLuc BacLuc closed this May 16, 2023
@BacLuc
Copy link
Owner Author

BacLuc commented May 16, 2023 •
edited
Loading

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
renovate
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@BacLuc