Vue 2 End Of Life

Posted on  by admin

Modified1 year, 2 months ago. Can I add something to beforeDestroy to prevent destroying the component? Or is there any way to prevent destroying the component ? my case is that when I change spa page by vue-route, I use watch route first, but I found that doesn't trigger because the component just destroy..

When is the Vue 3 Masterclass coming?

33 gold badges99 silver badges1919 bronze badges.

Should I learn Vue 2 or Vue 3 in 2021?

  • 1919 bronze badges.
  • As belmin bedak commented you can use keep-alive.
  • when you use keep-alive two more lifecycle hooks come into action, they are activated and deactivated hooks instead of destroyed. The purpose of keep-alive is to cache and to not destroy the component. you can use include and exclude atteibutes of the keep-alive element and mention the names of the components that shoulb be included to be cached and be excluded from caching. Here is documentation.

3636 gold badges175175 silver badges230230 bronze badges. 230230 bronze badges.

Bonus: Why does it take time for the ecosystem to be ready for Vue 3?

Although I would consider @Vamsi Krishna "keep-alive" answer to be the proper "VueJS way" to solve this issue, I was not willing to refactor part of my code for it.

I also couldn't use the Vue router navigation guard "as-is" because in the case of beforeRouterLeave, even though using next(false) prevented the route from continuing, the component in Vue was ALREADY destroyed.

#v2.7

  • Any state I had that wasn't saved would be lost, which defeats the purpose of cancelling the route change.
  • This wasn't what I wanted, as I needed the state of the form/settings in the component to remain (the component reloaded itself and kept the same route).
  • So I came up with a strategy that still used a navigation guard, but also cached any form changes/settings I had in the component in-memory, eg.

#v1.5

  • I add a beforeRouteLeave hook in the component:.
  • Outside the Vue component, I initialize _cachedComponentData.
  • Then in the created or mounted life cycle hooks, I can set the _cachedComponentData to "continue where the user left off" in the component:.
  • Hello all, I am looking for help. I am trying to find the right place to ask a question about Vue 1.X End Of Life support as I can’t find anything on the github repo. The only reference to something similar to an official EOL notice is in this blog update: https://vuejs.org/2016/04/27/announcing-2.0/.

#Released

“We are also not forgetting about 1.x! 1.1 will be released alongside 2.0 beta, with an LTS period of 6-month critical bug fixes and 9-month security updates.

#v2.6 (Horizon)

  • It will also ship with optional deprecation warnings to get you prepared for upgrading to 2.0.
  • I am checking the releases of vue and I can’t find the 1.1 release but there is a branch, which only seems to show a typo fix (https://github.com/vuejs/vue/compare/1.0..1.1).
  • Where’s the best place to ask for a official update on support (or lack of support) for Vue 1.X?

#v2.5 (Avalon)

  • Since the announcement of Vue 3 there are two questions I am frequently asked by newcomers and senior Vue developers.
  • Should I use or learn Vue 2 in 2021?
  • When is the Vue 3 Masterclass coming? The Vue.js Masterclass is how Vue School started. It was originally created in 2016 as the next step for the readers of my book, The Majesty of Vue.js.
  • The masterclass has taught Vue.js to 1000s developers and helped many of them land a relevant job. Also, many companies worldwide use the Vue Masterclass to train their teams, develop high-end front-end applications, and often for onboarding new employees.

#v2.4 (Endurance)

  • We implement everything, including user profiles, permissions, threads, content management, live updates, and whatnot!
  • The forum we build in the Masterclass is developed with Vue 2.
  • Vue 3.0, codename One Piece, was announced 2 years ago and was officially released in September 2020. Vue 3 is a complete rewrite of the framework. It comes with even better performance, better tree-shaking, smaller size, improved TypeScript support, and some revolutionary new features for developing large-scale enterprise software.
  • Thus, Vue 3 is awesome and was released a few months ago. But does this mean that we can or should use it in production just yet? In this article I try to address all these questions. Let’s begin with the first one. Most of the syntax and practices in Vue 2 remain the same in Vue 3, so it shouldn’t make a big difference if you learn Vue 2 or Vue 3.

#v2.3 (Liberator)

  • And in both cases you have a great phone!
  • Same in Vue.js, when you switch to Vue 3 you will be able to do more things with your new framework but everything you could do previously will continue to work.
  • And for making the switch, the Vue team will be releasing in-depth guides and a migration tool that will parse your application and guide you through the upgrade. So don’t be afraid of Vue 3 and stop hesitating learning and using Vue 2 in 2021.
  • Everybody uses Vue 2 in 2021! You won’t fall behind, you are not missing out, and your codebase is definitely not outdated. Keep your focus on developing amazing apps and when the Vue 3 ecosystem is ready for the migration we will all know it and we will have time in our turn to upgrade.

#v2.2 (Tigris)

  • We’re going to build our beloved forum from scratch again.
  • This time we will be using Vue 3 and all the latest and greatest ecosystem and other 3rd party libraries we need in order to build a modern Real-World application.
  • It was technically possible that we released the new course while Vue 3 or the ecosystem is experimental. But that’s not what the Masterclass is about. The goal is to teach you stable code and best practices for production. Not code that might change tomorrow or next month. You can find the Vue 3 Masterclass here.
  • The original course is developed with Vue 2 and the content is still relevant, you can use it at work today! Though, as the course is years old you will have to do some workarounds here and there which might be a bit annoying. We’ve taken all the feedback we got from The Vue.js 2 Masterclass, and supercharged The Vue.js Masterclass with all the new goodies from Vue.js 3 and the ecosystem.

#v2.1 (Vanguard)

  • The core (official) libraries are planed to release a vue 3 version by the end of 2020.
  • But that’s just for the core libraries that are maintained by the Vue team.
  • There are thousands of Open Source creators out there that have created great libraries for Vue.js we all use every day. What happens with them? They have to put in a lot of time and effort to create a new major version of their project where they code it, improve it, test it, write documentation, and repeat until it is ready to be used in production.
  • And this is a big responsibility. Vue.js is used in a massive number of websites including some huge organisations like Microsoft, Apple, Google, and Nintendo to name a few. The Vue 3 API for most Vue developers does not introduce breaking changes.

#v2.0 (Arcadia)

  • So if your company needs to have Vue 3 support for a specific library soon, you should consider supporting the maintainers via Patreon, Open Collective, or GitHub sponsors.
  • Notes:v2.0 Release
  • Overview:A complete rebuild of the framework core. Improving the layout and theme systems, platform integration, accessibility, RTL and performance. Update all components to the Material Design 2 specification. Add additional functionality to multiple existing components and setup v1.5 for Long-term Support.
  • Objectives:
    • Add new components
      • v-app-bar
      • v-banner
      • v-chip-group
      • v-color-picker
      • v-file-input
      • v-list-item-group
      • v-overlay
      • v-simple-table
      • v-slide-group
    • Complete update to Material Design 2
    • Convert from Javascript to Typescript
    • Convert from Stylus to Sass
    • Convert from avoriaz to vue-test-utils

#Archived

The following releases are old and unsupported minor and major versions:

#v1.4

  • Released: December 2018
  • Notes:v1.4 Release
  • Overview:Added new components v-sparkline and abstracted v-toolbar's functionality into multiple components for easier maintainability and testing. Rebuilt the entire documentation to make it easier for contributors and maintenance from the team.

#v1.3

  • Released: December 2018
  • Notes:v1.3 Release
  • Overview:Added new components, v-treeview, v-timeline and v-item-group. Unified the interfaces used in v-tabs and v-carousel. Improved the vuetify-loader to support effortless application tree-shaking of Vuetify components.

#v1.2

  • Released: October 2018
  • Notes:v1.2 Release
  • Overview:Added new components, v-img, v-rating and v-hover. Improved theme propagation system and expanded the functionality of the colors used with components such as HEX and RGBA. Als added numerous new locales.

#v1.1

  • Released: July 2018
  • Notes:v1.1 Release
  • Overview:A complete rebuild of all form functionality including all inputs and selection controls. Abstracted features from components like v-select into new implementations, v-autocomplete, v-combobox for more scoped functionality and easier testing. This release also marked the first official support of RTL languages.

#v1.0

  • Released: February 2018
  • Notes:v1.0 Release
  • Overview:The official v1.0 release party. After 18 months and Kael’s sanity, we rolled into our first MAJOR release. This included a multitude of brand new components, features and functionality.

#Alpha release

  • Released: December 2016
  • Overview:Vuetify is officially announced to the public. The framework initially shipped with 40 components and came in at a whopping 46kb.

Ready for more?

Continue your learning with related content selected by the Team or move between pages by using the navigation links below.
Edit this page on GitHub
Last updated:04/26/2022, 5:01:14 PM